Data collection display system and data collection display method

Abstract

To provide a system and method for reducing time and effort for specifying onsite data if a product is defective.SOLUTION: In a data collection display system 100, an information system 1 includes an onsite data storage unit for storing onsite data, a relevancy data storage unit for relating a task to the onsite data related to the task, a model creation unit for updating a model history for managing version identifiers of a plurality of process models and the version identifiers each time the process models are updated, a relevancy data registration unit for registering relevancy data on the basis of a process model corresponding to a specific version identifier from the plurality of process models, a model retrieval unit for retrieving model information from the model history with the version identifier or date and time corresponding to the updated process model as a retrieval key, and a provision data generation unit for specifying the task and the onsite data related to the task from the relevancy data related to the process model corresponding to the model information, and externally providing the specified task and onsite data.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a data collection and display system and a data collection and display method, and is suitably applied to a data collection and display system that collects field data from field data generating devices installed in production facilities of a factory, for example. [Background technology]

[0002] In recent years, a large number of data collection devices are installed on the production lines of production facilities in factories, and on-site data is collected in real time using these data collection devices. The on-site data collected in this way is accumulated as a data lake on a platform.

[0003] In order to investigate the cause of a defect in a product produced on a production line, it is necessary to analyze, based on the relevant on-site data, what business process the product was manufactured under and how each business was performed. However, since the business process changes over time, the business model for managing the business process must also be updated as the business process changes and version management must be performed. As a method for version management of a business model, there is a method described in Patent Document 1. Patent Document 1 adopts a management method that links the version of the business model and on-site data based on the operation start and end dates and times of the business model. If a product is defective, on-site data about the defective product is obtained based on the operation start and end dates and times of the business model for each version of the business model, and is used to investigate the cause. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2005-111198 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the method disclosed in Patent Document 1, it was necessary to specify the operation start and end dates and times of the business model for each version of the business model, find the previous business model corresponding to the defective product, and identify the on-site data corresponding to the previous business model. This was time-consuming to identify the on-site data related to the defective product.

[0006] The present invention has been made in consideration of the above points, and aims to propose a data collection and display system and a data collection and display method that can reduce the effort required to identify on-site data even when a product is defective. [Means for solving the problem]

[0007] In order to solve the above problem, the present invention includes a site data storage unit for storing site data, a relationship data storage unit for storing a plurality of relationship data for managing relationships between tasks, the relationship data storing unit storing a plurality of relationship data that associates a task node corresponding to the task with the site data related to the task, a version management unit for managing version identifiers of the plurality of process models in association with model information of the plurality of process models, a version identifier update unit for updating the version identifier managed in the version management unit in association with model information of the updated process model every time any one of the plurality of process models is updated, the version identifier updated each ... model search unit for searching the version management unit using the version identifier or date and time corresponding to the updated process model as a search key, and searching the plurality of process models for model information matching the search key, and a provided data generation unit for identifying the task and the site data related to the task from the relationship data related to the process model corresponding to the model information, and providing the identified task and the site data related to the task to an outside party.

[0008] Also, in the present invention, a data collection and display method of a data collection and display system that collects field data includes a field data accumulation step in which the field data is accumulated in a field data accumulation unit, a relationship data accumulation step in which data for managing relationships between tasks is accumulated in a relationship data accumulation unit, the relationship data being data for associating a task node corresponding to the task with the field data related to the task, a version management step in which a version management unit is used to manage version identifiers of the multiple process models in association with model information of the multiple process models, and a version identifier update unit updates the version identifier of the multiple process models in association with model information of the updated process model every time any one of the multiple process models is updated. the version identifier updating step of updating the version identifier managed in a version management unit; a relationship data registration step of registering relationship data in a relationship data registration unit based on model information of a process model corresponding to a specific version identifier from among the plurality of process models; a model information search step of a model search unit searching the version management unit using the version identifier or date and time corresponding to the updated process model as a search key, and searching the plurality of process models for model information matching the search key; and a provided data generation step of a provided data generation unit identifying the business and on-site data related to the business from the relationship data related to the process model corresponding to the model information, and providing the business to an external party.

[0009] According to the present invention, when investigating the cause by comparing the field data of a defective product and the products before and after it, even if the process model when the field data for the defective product was created is different from the process model when the field data for the defective product was created, the field data for the previous and next products can also be searched for based on the process model when the field data for the defective product was created. Therefore, even if a product is defective in a situation where the process model is updated sequentially, the effort required to investigate the cause of the product defect can be reduced. Effect of the Invention

[0010] According to the present invention, it is possible to realize a data collection and display system and a data collection and display method that reduce the time and effort required to identify on-site data even when a product is defective. [Brief description of the drawings]

[0011] [Figure 1] 1 is a block diagram showing an example of a system configuration of a data collection and display system according to an embodiment of the present invention. [Diagram 2] 1 is a block diagram showing an example of the functions of an information collection and display system according to an embodiment of the present invention; [Diagram 3] FIG. 2 is a diagram illustrating an example of a data structure of a process model. [Figure 4A] FIG. 13 is a schematic diagram showing an example of updating a process model. [Figure 4B] FIG. 13 is a schematic diagram showing an example of updating a process model. [Figure 4C] FIG. 13 is a schematic diagram showing an example of updating a process model. [Figure 4D] FIG. 13 is a schematic diagram showing an example of updating a process model. [Diagram 5] FIG. 2 is a diagram illustrating an example of a data structure of relationship data. [Figure 6] FIG. 13 is a diagram illustrating an example of an update sequence of a process model. [Figure 7] FIG. 13 is a diagram illustrating an example of a version-specified process model search sequence. [Figure 8] FIG. 11 is a diagram illustrating an example of a registration sequence of association data. [Figure 9] FIG. 11 is a diagram showing an example of a search sequence for relevance data and site data. [Figure 10] FIG. 13 is a diagram showing an example of a search screen for process models and site data. [Figure 11] FIG. 13 is a diagram showing an example of a search screen for process models and site data. [Figure 12A] FIG. 13 is a diagram showing an example of a model history table constituting a model history. [Figure 12B] FIG. 13 is a diagram showing an example of a model history table constituting a model history. [Figure 12C] FIG. 13 is a diagram showing an example of a model history table constituting a model history. [Figure 13A] FIG. 13 illustrates an example of a model history table. [Figure 13B] FIG. 13 illustrates an example of a model history table. [Figure 13C] FIG. 13 illustrates an example of a model history table. [Figure 13D] FIG. 13 illustrates an example of a model history table. [Figure 14] FIG. 11 is a diagram showing an example of a search sequence for relevance data and site data according to a modified example of this embodiment. [Figure 15] FIG. 13 is a diagram showing an image of searching for association data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] An embodiment of the present invention will now be described in detail with reference to the drawings.

[0013] 1 is a block diagram showing an example of a system configuration of a data collection and display system 100 according to this embodiment. The data collection and display system 100 includes data generating devices 6a, 6b, and 6c, a model data storage unit 3, a relationship data storage unit 4, a site data storage unit 5, and a network 2. The data generating devices 6a, 6b, and 6c, the model data storage unit 3, the relationship data storage unit 4, and the site data storage unit 5 are connected to each other via the network 2. When the data generating devices 6a, 6b, and 6c are not particularly distinguished from each other, they are simply referred to as data generating devices 6.

[0014] The data generating device 6 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 6a), a sensor that collects inspection information of an RFID (Radio Frequency IDentifier) ​​attached to a part or a product (finished product) (for example, data generating device 6c), a machine that processes parts or assembles a finished product (for example, data generating device 6c), etc. On-site data as actual data collected or generated by these data generating devices 6 is transmitted to the information system 1, the model data storage unit 3, or the on-site data storage unit 5 via the network 2.

[0015] The model data storage unit 3 is, for example, a storage device such as a server or memory, and stores a process model (hereinafter, also simply referred to as a "model") that defines what information is to be stored in the site data storage unit 5 or the like. This model is also referred to as master data. The process model is updated over time and is managed by version. By changing the model defined in the model data storage unit 3, it is possible to change what site data (type of information to be collected) is to be collected from the data generating devices 6a, 6b, 6c. The model in this model data storage unit 3 can be set or changed via an external device (not shown).

[0016] The on-site data accumulation unit 5 is, for example, a storage device such as a server or a memory, and accumulates on-site data including information defined by the model in the model data accumulation unit 3. In this embodiment, on-site data is accumulated in the on-site data accumulation unit 5. The on-site data is, for example, data such as identification information of the type of on-site data acquired by the data generating device 6, the date and time of occurrence, and actual measured values.

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

[0018] 2 is a block diagram showing an example of functions of a data collection and display system 100 according to this embodiment. The data collection and display system 100 includes a data registration device 7, a relationship data registration unit 12, a relationship data storage unit 4, a provided data generation unit 16, a data providing interface 15, a model data storage unit 3, a model creation unit 11, a model management interface 10, a model search unit 14, and a model search interface 13. The data registration device 7 and the provided data generation unit 16 acquire on-site data from the on-site data storage unit 5.

[0019] The model data storage unit 3 includes a latest version model 3A, an editing model 3B, and a model history 3C. The editing model 3B manages a process model that has started updating and is currently being updated among a plurality of process models. The latest version model 3A manages a latest version process model where the update of the editing model has been completed. The model history 3C is an example of a version management unit, and manages at least the version identifiers of a plurality of process models in association with model information of the plurality of process models. However, the latest version model 3A is the latest model of the model history 3C, and it is not necessary to manage the latest version model 3A and the model history 3C separately.

[0020] The model creation unit 11 has a function of creating a latest version model 3A, an editing model 3B, and a model history 3C. When the model creation unit 11 starts updating a process model to be updated among a plurality of process models, the model creation unit 11 sets the process model to be updated as an editing model 3B, and registers in the model history 3C that the process model to be updated is being updated. Furthermore, when the model creation unit 11 completes the update of the process model to be updated, the model creation unit 11 sets the process model to be updated as the latest version model 3A, and registers in the model history 3C that the update has been completed for the process model to be updated. In the model history 3C, a version identifier indicating the version of the updated process model is also registered together with model information of the process model to be updated.

[0021] The model management interface 10 is a user interface such as a display, and has a function of displaying the latest version model 3A, the model being edited 3B, and the model history 3C created by the model creation unit 11 on the user's operation terminal 8. The model management interface 10 is also configured to allow the user to input predetermined information and operations to the model creation unit 11. Alternatively, the model management interface 10 may be an API (Application Programming Interface) that sends and receives information based on a predetermined data structure.

[0022] The above-mentioned model history 3C is an example of a version management unit, and manages version identifiers that represent the version histories of the multiple process models. The model creation unit 11 is an example of a version identifier update unit, and each time any one of the multiple process models is updated, the model creation unit 11 updates the version identifier of the process model managed in the model history 3C in correspondence with the model information of the updated process model.

[0023] The model search unit 14 has a function of searching for information relating to the latest model 3A, the model being edited 3B, and the model history 3C. The model search interface 13 is a user interface such as a display, and has a function of presenting information relating to the latest model 3A, the model being edited 3B, and the model history 3C searched for by the model search unit 14 to the application 9. Alternatively, the model search interface 13 may be an API (Application Programming Interface) that exchanges information based on a predetermined data structure.

[0024] The model search unit 14 is an example of a model information search unit, and has a function of extracting a specific process model that may be related to the version identifier corresponding to the updated process model, using the version identifier corresponding to the updated process model or the date and time (search date and time) as a search key, in accordance with the search conditions for the updated process model.

[0025] As described above, the data registration device 7 acquires the site data from the site data storage unit 5 , and passes the site data to the related data registration unit 12 .

[0026] The relationship data registration unit 12 can acquire on-site data from the data registration device 7, and has the function of acquiring models (the latest model 3A, the model being edited 3B, and the model history 3C) searched by the model search unit 14 via the model search interface 13.

[0027] The relationship data registration unit 12 is an example of a relationship data registration unit, which manages relationship data for managing the relationships between multiple field data, and registers the relationship data based on a specific version of a process model obtained via the model search interface 13.

[0028] The relationship data registration unit 12 creates definition information based on the model input from the model search interface 13 and the process model from the model data storage unit 3. The definition information created by the relationship data registration unit 12 has a predetermined data structure, and defines the data structure in which the relationship data registration unit 12 acquires the site data from the data generating device 6.

[0029] The relational data registration unit 12 receives the site data from the data generating device 6 and structures the site data based on the data structure defined by the definition information. The relational data registration unit 12 then determines whether the site data acquired according to the definition information is business information, worker, machine, work procedure, or material (parts) based on the identification information given to the site data. Hereinafter, these 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).

[0030] Here, the relationship between the 4M information and the identification information assigned to the site data is defined in the relationship data registration unit 12, and based on this definition, the relationship data registration unit 12 associates the 4M information determined by the relationship data registration unit 12 with the site data actually acquired (maps the identification information of the site data to the 4M information). The relationship data registration unit 12 registers the 4M information after the site data has been associated with it in the relationship data storage unit 4. Furthermore, the relationship data registration unit 12 includes a temporary storage unit, and the temporary storage unit stores information for configuring the connection relationship (generating connection lines) between each piece of information (business information and 4M information) included in the site data.

[0031] The provided data generating unit 16 acquires site data from the site data storage unit 5 based on the relational data 500 stored in the relational data storage unit 4 .

[0032] When a user selects 4M information for a specific business from the model search interface 13, the relationship data registration unit 12 searches for other 4M information for business related to the 4M information based on the identification information given to the 4M information, and presents the searched 4M information to the user by displaying it in the user interface with hatching, color coding, etc. The relationship data registration unit 12 also registers in the relationship data accumulation unit 4 the connection relationship between the selected 4M information and the searched 4M information.

[0033] As described above, the provided data generation unit 16 acquires site data from the site data accumulation unit 5. The provided data generation unit 16 acquires relationship data from the relationship data accumulation unit 4. The relationship data is data that manages the relationship between tasks, and associates task nodes corresponding to tasks with site data. The provided data generation unit 16 acquires the model history 3C from the model data accumulation unit 3. Specifically, the provided data generation unit 16 acquires information regarding the version of the updated model from the model history 3C.

[0034] The provided data generation unit 16 is an example of a provided data generation unit, and acquires specific relationship data based on the process model extracted by the model search unit 14 via the model search interface 13. The provided data generation unit 16 identifies a predetermined number of site data managed by the specific relationship data, and provides the site data to the outside, i.e., the application 9, via the data providing interface 15. The user can grasp the site data via the application 9. Here, the data providing interface 15 may be a GUI (Graphical User Interface) that provides an input and display screen to the user, or may be an API that exchanges information based on a predetermined data structure.

[0035] The relational data storage unit 4 stores the connection relationship between the selected task information and 4M information transmitted from the relational data registration unit 12. The provided data generation unit 16 transmits to the application 9 other 4M information of a task related to the selected task information or 4M information, or on-site data acquired based on the task information or 4M information of another related task, based on the connection relationship between the task information and 4M information stored in the relational data storage unit 4, thereby enabling the task information or 4M information spanning multiple tasks to be used in various analysis methods.

[0036] In the data collection and display system 100, the provided data generating unit 16 transmits data associated by the association data 500 to the application 9 via the data providing interface 15. Here, the provided data generating unit 16 is connected to a dictionary database. Here, the item names of 4M information used in each manufacturing process (business) may differ for each manufacturing process. For this reason, 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 a dictionary database (not shown), and the provided data generating unit 16 can accurately acquire data associated by the association data 500, including not only the same words but also different words with the same meaning.

[0037] Next, an example of the data structure of the process model 300 managed by the data collection and display system 100 will be described. Fig. 3 is a diagram for explaining an example of the data structure of the process model 300. This process model 300 is data stored in the model data storage unit 3. The process model 300 is composed of tasks constituting a business process such as manufacturing tasks or logistics tasks, components of 4M related to the tasks and their relationships, data items related to each task or 4M, and management information of on-site data corresponding to the data items.

[0038] The process model 300, by using its data structure to associate at least one piece of on-site data generated from various devices (data generating device 6) in each manufacturing process, can show how workers, machines, parts, etc. are related to a specific task (manufacturing process) in a certain work procedure. In this embodiment, the process model 300 includes a task node 310 at the center, an input product node 320 indicating materials required to execute the task, a worker node 330 that executes the task, a facility node 340 used to execute the task, a work procedure node 350 that defines the execution procedure of the task, and an output product node 360 ​​generated as a result of executing the task using parts as materials. The output product node 360 ​​generated by executing the task node 310 becomes a material (part) used in the task node 312 of the subsequent process, and the input product node 320 that becomes the material of the task node 310 is a finished product generated in the task node 311 of the previous process. In other words, the input product node 320 and the output product node 360 ​​have the same meaning in terms of attributes, and when there is no particular distinction between the two, they may be collectively called material nodes. As described above, the input product node 320, worker node 330, equipment node 340, and work procedure node 350 are called 4M information or 4M nodes. Data items related to each task or 4M and management information for the site data corresponding to the data items are composed of, for example, the data item name, the IP address or database (DB) name of the corresponding site data storage unit, the table name, the column name, etc., as shown in the site data management information 370.

[0039] The relationship data 500 has a structure similar to that of the process model 300, and is composed of the identification information of the business object and the identification information of the 4M information for each business object of each business, and the relationship between them. For example, when the business in the process model is an assembly business, the business object is a product to be assembled, and the identification information of the business object is the serial number or lot number of the product. For example, among the 4M information, the identification information of the input product is the serial number or lot number of the parts used in the assembly, and the identification information of the equipment is an identifier for identifying the performance value when assembling the product in the equipment used in the assembly work. In the data collection and display system 100, when a problem occurs in the product itself, the 4M information associated with the finished product can be searched for by the relationship data 500, and the cause of the problem in a specific manufacturing process (business) can be found. In this embodiment, a case will be described in which identification information is given to the on-site data collected or generated by the data generating device 6 in each manufacturing process. In the data collection and display system 100, the relationship between the businesses can be managed by accumulating the relationship data 500 that defines the relationship between the business and the machine, the worker, etc. across multiple manufacturing processes (businesses).

[0040] Basic information of this association data 500 is identification information indicating each piece of information and timing (date and time) related to the association between the identification information. On-site data (actual data) indicated by each identification information of the association data 500 is stored in an on-site data storage unit 5 managed externally, and the method of accessing the on-site data stored in the on-site data storage unit 5 is managed by the data collection and display system 100 using the on-site data management information 370 in the process model 300.

[0041] The aforementioned relational data is composed of business nodes 310 and 4M information. The connection lines connecting the nodes have as inputs what is necessary to execute the business and as outputs the finished products generated by the actions of those inputs, and this is expressed as a directed graph.

[0042] 4A to 4D are schematic diagrams showing an example of updating a process model. A first process model version 401 shown in FIG. 4A represents the version of the process model from 9:00 on October 10, 2022 to 08:30 on November 1, 2022 of the first process model. When a new task D and a new equipment D are added between the task C and the product X in the process model shown in FIG. 4A, it becomes a second process model shown in FIG. 4B.

[0043] The second process model version 402 shown in FIG. 4B indicates the version of the process model of the second process model from 08:30 on November 1, 2022 to 18:00 on January 10, 2023. When the tasks A and B are integrated into the task E to improve work efficiency, the third process model shown in FIG. 4C is obtained.

[0044] The third process model version 403 shown in FIG. 4C indicates the version of the process model of the third process model from 18:00 on January 10, 2023 to 9:00 on February 1, 2023. When the column "value3" is added to the site data of facility C by adding a management item, the fourth process model shown in FIG. 4D is obtained. This fourth process model version 404 indicates the version of the process model of the fourth process model from 9:00 on February 1, 2023.

[0045] In this embodiment, the process model can be updated by the model creation unit 11 over time as described above, and the model creation unit 11 manages the version of the process model as a version identifier every time the process model is updated, and stores the version identifier in the model history 3C in association with the updated process model. Here, the process model can be updated when a change (addition, deletion, change) occurs in any of the components of the business or 4M, the information of the data items held by each business or 4M, the management information of the field data corresponding to the data items, the order of business operations, or the information of the relationship between the business operations and 4M, as shown in the examples of Figures 4A to 4D.

[0046] 5 is a diagram for explaining an example of the data structure of the relationship data, in which the example shows relationship data corresponding to a plurality of tasks before and after the task.

[0047] The relationship data shown in the figure relates to a certain task and a subsequent task downstream, and is centered around a task node 501. It includes an input product node indicating the materials needed to perform the task, edge 511, a worker node 503 that performs the task, edge 513, an equipment node 504 used to perform the task, edge 514, a work procedure node 505 that defines the procedure for performing the task, edge 515, and an intermediate product node 506 that is the output product generated as a result of performing the task using parts as materials.

[0048] The business node 501 is located at the center of the business, and is used to obtain a worker node 503, an equipment node 504, and a work procedure node 505 as examples of field data, which are connected by edges 513, 514, and 515, respectively.

[0049] In addition, intermediate product node 506 generated by executing business node 501 becomes a material (part) used in business node 510 of the subsequent process, and intermediate product node 506, which is the finished product of business node 501, becomes a material (part) used in business node 510 of the subsequent process.

[0050] The relationship data shown in the figure includes an edge 512 for the downstream process business, with a business node 510 at the center, an intermediate product node 506 as an input product node indicating the materials required to carry out the business, and a finished product node 502 as an output product generated as a result of carrying out the business using parts as materials.

[0051] Next, an overview of an information collection and display method of the data collection and display system 100 according to this embodiment will be described. As described above, the data collection and display system 100 collects field data generated by the data generating device 6. This information collection and display method includes a field data accumulation step in which field data is accumulated in a field data accumulation unit 5, a relationship data accumulation step in which data for managing relationships between tasks, the relationship data being data for associating task nodes corresponding to tasks with field data related to the tasks, is accumulated in a relationship data accumulation unit 4, a version management step in which a model history 3C as an example of a version management unit is used to manage version identifiers of the multiple process models in association with model information of the multiple process models, and a model creation unit 11 as an example of a version identifier update unit updates any one of the multiple process models, corresponding to the model information of the updated process model, and manages the model identifiers of the multiple process models in association with the model information of the updated process model. The system includes a version identifier updating step for updating the version identifier managed in the history 3C, a relationship data registering step in which the relationship data registering unit 12 registers relationship data in the relationship data storage unit 4 based on model information of a process model corresponding to a specific version identifier from among a plurality of process models, a model information searching step in which the model searching unit 14 searches the model history 3C using a version identifier or date and time corresponding to the updated process model as a search key, and searches the plurality of process models for model information matching the search key, and a provided data generating step in which the provided data generating unit 16 identifies the task and on-site data related to the task from the relationship data related to the process model corresponding to the model information, and provides the task to an external party. Each step will be specifically described below.

[0052] 6 is a diagram showing an example of a process model update sequence. First, in step S601, when the operation terminal 8 makes a request to start updating the process model in response to a change in the manufacturing process or the like, the request to start updating is received by the model creation unit 11 via the model management interface 10. Here, even in the middle of the process model update work, there is a possibility that registration of association data from the data registration device 7 occurs. At this time, in order to avoid registering association data based on the process model in the middle stage, in step S602, the process model update work is performed on the model being edited 3B.

[0053] Next, in step S603, when the operation terminal 8 confirms the editing of the process model, the request for confirming the editing is received by the model creation unit 11 via the model management interface 10. In step S604, the model creation unit 11 makes the currently edited model 3B the latest model 3A based on the request for confirming the editing.

[0054] Next, in step S605, the model creation section 11 adds the model being edited 3B together with the version identifier of the process model to the model history 3C, thereby updating the model history 3C.

[0055] 7 is a diagram showing an example of a version-specified process model search sequence, in which model information of a process model is searched for as a table of contents for searching on-site data.

[0056] First, in step S701, the application 9 makes a search request specifying a version identifier or date and time of a process model, for example, for the purpose of acquiring on-site data related to a defective product. The search request is received by the model search unit 14 via the model search interface 13.

[0057] Next, in step S702, the model search unit 14 makes a search request to the model history 3C based on the search request, using the version identifier of the process model or the date and time as a search key. Then, in step S703, if a model history corresponding to the version identifier or date and time of the above process model exists in the model history 3C, the model search unit 14 receives the version identifier of the process model as a response.

[0058] Next, in step S704, the model search unit 14 makes a search request for model information linked to the version identifier of this process model. Note that step S704 may be executed together with step S702 and integrated into step S702. In step S705, in response to the request, if model information linked to the version identifier of this process model exists in the model history 3C, the model search unit 14 receives the model information.

[0059] Next, in step S706, the model retrieval unit 14 returns the model information to the application 9 via the model retrieval interface 13.

[0060] 8 is a diagram showing an example of a registration sequence of relational data. As described above, the site data is sequentially stored in the site data storage unit 5. In step S801, the data registration device 7 acquires the site data from the site data storage unit 5. In step S802, the data registration device 7 registers the site data in the relational data registration unit 12. Here, the data registration device 7 may register the site data by mainly specifying the version identifier of the process model, or may register the site data without specifying the version identifier of the process model.

[0061] In step S803, the relationship data registration unit 12 makes a search request for model information to the model search unit 14 via the model search interface 13. Next, in step S804, when the model search unit 14 receives the search request for the model information via the model search interface 13, it determines the search destination. Here, if a version identifier (or date and time) of the process model is specified, the model search unit 14 searches for model information corresponding to the version identifier. On the other hand, if no such specification is made, the model search unit 14 searches for the latest version model 3A as the search destination. This is for the purpose of acquiring model information in order to determine the registration contents (connection destination) of the relationship data.

[0062] Here, the latest model 3A reflects the latest on-site business process and 4M information, and the on-site data storage unit 5 stores on-site data based on the current on-site situation, so the relationship data registration unit 12 registers the relationship data corresponding to the latest model 3A unless otherwise specified. On the other hand, there are cases where the relationship data is registered after a certain time has passed since the generation of the on-site data by batch processing or the like, and in that case, the registered on-site data may not be the latest model 3A but may be the on-site data generated in a past process model stored in the model history 3C, so the configuration is such that it is also possible to register the relationship data specifying the version or date and time of the process model.

[0063] Based on the response to the model information, the relationship data registration unit 12 can identify a process model corresponding to the model information. In step S807, the relationship data registration unit 12 creates relationship data based on the model information of the identified process model, and registers the data in the relationship data storage unit 4. The registration here can be exemplified by registering a business node of business B having a certain business object identifier and connecting it to an output product node that is an output of a business node of business A having the same business object identifier.

[0064] Next, in step S808, the relationship data registration unit 12 registers the relationship data in the relationship data storage unit 4. This registration results in registration of relationship data that depends on the process model of the model information. Next, in step S809, the relationship data registration unit 12 responds to the data registration device 7 with the registration result.

[0065] FIG. 9 is a diagram showing an example of a search sequence for relevance data and site data.

[0066] In step S901, the application 9 requests the provided data generator 16 to search for site data specifying the version of the process model via the data providing interface 15. The application 9 specifies the search conditions for the process model and the search conditions for the site data. For example, in the process model for November, the site data for Task A in October and November is used as the starting point to obtain the site data for Tasks A, C, and D.

[0067] In step S902, when the provided data generation unit 16 receives the search request via the data provision interface 15, the provided data generation unit 16 sends a search request to the model search unit 14 via the model search interface 13 to search for model information based on the search conditions for the process model.

[0068] In step S903, the model search unit 14 searches the model history 3C for model information that specifies the version or date and time of the process model. The model search unit 14 checks whether the search target business or 4M data items included in the search conditions for the site data exist, and searches the model information to obtain management information for the site data.

[0069] In step S904, the model retrieval unit 14 acquires model information as a model response from the model history 3C (step S905). The model retrieval unit 14 provides the model information to the provided data generation unit 16 via the model retrieval interface 13.

[0070] In step S906, the provided data generation unit 16 searches for related data based on the search conditions for the site data. In step S907, the relationship data accumulation unit 4 responds with relationship data that matches the search conditions. In step S908, the provided data generation unit 16 makes a search request for site data using the identification information of the site data included in the relationship data as a search key, and receives a response of the site data from the site data accumulation unit 5 (step S909). Note that in this embodiment, it is not necessary to repeatedly execute the above-mentioned steps S903 to S909 the number of times corresponding to the version identifiers of the corresponding process model.

[0071] In step S910, the provided data generation unit 16 generates provided data by linking the plurality of on-site data associated with each other by the association data in response to the on-site data. In step S911, the provided data generation unit 16 provides the provided data to the application 9 via the data providing interface 15.

[0072] 10 is a diagram showing an example of a process model and site data search screen 1000. The process model and site data search screen 1000 is a screen generated using the model search interface 13 and the data provision interface 15, and includes an input field for searching for an updated process model by specifying a date and time, and a selection field for searching by specifying a version identifier, as search conditions for an updated process model. Specifically, the process model and site data search screen 1000 has a process model search condition field 1001, a process model update history field 1002, a process model display field 1003, and a trace start point search condition field 1004.

[0073] The process model and site data search screen 1000 acquires the process model corresponding to the version searched from the process model search condition field 1001 or the process model update history field 1002 from the model search unit 14 via the model search interface 13, and visually displays it in a process model display field 1003. The process model and site data search screen 1000 accepts the selection of a part of the business nodes of the process model displayed in the process model display field 1003, and displays a trace start point search condition field 1004 in which search conditions of the trace start point for tracing the site data for the part of the process model that accepted the selection can be entered.

[0074] The process model search condition field 1001 has a search condition input field 1001a for inputting date and time, and a search start button 1001b. When the search start button 1001b is pressed with date and time input in the search condition input field 1001a as a search condition for a process model, if a corresponding process model is found, the process model is displayed in the process model display field 1003. The business node ("Business A" in the figure) and 4M data items ("Equipment A" and "Material A" in the figure) displayed in the process model display field 1003 are selectable.

[0075] The process model update history field 1002 has radio buttons 1002b to 1002d of process model candidates and a reflect button 1002a. When a process model candidate is selected with any of the search process model candidate radio buttons 1002b to 1002d as a process model search condition and the reflect button 1002a is pressed, if a corresponding process model is found, the process model is displayed in the process model display field 1003. Similarly, the business nodes and 4M data items displayed in the process model display field 1003 are selectable.

[0076] That is, in order to search for a process model, it is necessary to input search conditions in either the process model search condition field 1001 or the process model update history field 1002. Here, the description will be given assuming that search conditions are set in the process model update history field 1002.

[0077] In the trace start point search condition field 1004, a search condition for a trace start point for searching for site data related to a selected business node, etc. (in the illustrated example, "Business A" is selected) is input. In the illustrated example, as the search condition for the trace start point, "October 1, 2022, 00:00" is input as the start date and time, and "November 30, 2022, 23:59" is input as the end date and time. When the setting button 1004a is pressed with the search condition for the trace start point set in this way, the search condition for the process model is set based on the search condition set in the process model update history field 1002, and the search condition for the association data and the corresponding site data is set based on the search condition for the trace start point set in the trace start point search condition field 1004.

[0078] 11 is a diagram showing an example of a search screen for process models and site data. When the setting button 1004a for the search condition of the trace starting point is pressed on the process model and site data search screen 1000 shown in FIG. 10, the above-mentioned search condition "second process model", the start date and time "October 1, 2022 00:00" which is the search condition of the trace starting point, and the end date and time "November 30, 2022 23:59" are displayed in the process model display field 1003 together with the hit process model. In the following description, the start date and time to the end date and time are referred to as the specified period.

[0079] On the process model and field data search screen shown in the figure, field data can be searched by selecting the business node or 4M data item to be searched. The search items displayed in the search item setting fields 1005 and 1007 are the items defined as the data items of each business node and 4M in the second process model. For example, when the business node Business D is selected, the search item setting field 1007 in the upper right corner of the figure is displayed.

[0080] The search item setting column 1007 includes a planned start date and time, a planned end date and time, an actual start date and time, and an actual end date and time as check boxes 1007b for setting search items.

[0081] The search item setting field 1007 has a setting button 1007a, and when the setting button 1007a is pressed, search items are displayed in the search item field 1006 according to the settings of the check boxes 1007b.

[0082] Furthermore, when one of the data items in 4M is selected ("equipment C" in the illustrated example), a check box 1005b for selecting, for example, "equipment C performance" and check boxes 1005c for selecting "product ID", "set value", and "measured value" for the equipment C table are displayed as a search item setting field 1005 shown in the center right side of the figure. The search items displayed here indicate that equipment C performance is defined as a data item possessed by equipment C in the second process model, and that equipment C performance is stored in the field data accumulation unit as an equipment C table, with its columns consisting of product ID, set value, and measured value. At this time, by selecting the equipment C performance check box, all columns in the equipment C table can be checked. Alternatively, only necessary columns can be selectively checked.

[0083] The search item setting field 1005 has a setting button 1005a. When the setting button 1005a is pressed, search items are displayed in a search item field 1006 according to the settings of the check boxes 1005b and 1005c.

[0084] When the search button 1006a of the search item field 1006 is pressed with the search item displayed in the search item field 1006, the sequence of FIG. 9 described above is executed. At this time, the version identifier (or update date and time) of the second process model is set as the search condition of the process model, and the search condition of the site data is set to search for association data from "October 1, 2022, 00:00" to "November 30, 2022, 23:59" as the execution period of the site data, with the trace starting point being the business A. Furthermore, as the search condition of the site data, it is set to obtain the actual start date and time of the business A, the actual end date and time of the business C, and the actual end date and time of the business D based on the association data that matches the search condition of the trace starting point. Based on this condition, the result of the sequence of FIG. 9 being executed is displayed in the search result field 1008 shown in the lower part of FIG. 11. In the search result field 1008, data corresponding to the search items set as search items in the search item field 1006 are displayed in a linked state based on the association data.

[0085] In this embodiment, even when searching for site data based on the second process model version, the search conditions for the site data can include the set period of the first process model version. Furthermore, for the site data of task D that exists in the second process model version but does not exist in the first process model version, as a result of searching for product 1 and product 2, the product ID is left blank as shown in the search result field 1008, and a response is made indicating that there is no site data.

[0086] FIG. 15 is an image diagram of searching for relationship data based on the search conditions shown in FIG. 11. For example, in the first process model, if products with product IDs of product 1 and product 2 are manufactured, the relationship data accumulation unit accumulates relationship data 1501 and 1502 corresponding to product 1 and product 2 based on the first process model. Similarly, in the second process model, if products with product IDs of product 3 and product 4 are manufactured, the relationship data accumulation unit accumulates relationship data 1503 and 1504 corresponding to product 3 and product 4 based on the second process model. When the tracing start point is business A and relationship data from "October 1, 2022, 00:00" to "November 30, 2022, 23:59" is searched for as the implementation period of business A, the relationship data of business A corresponding to product 1, product 2, product 3, and product 4 meets the condition. The links in the related data that meet the conditions are traced, and the performance start date and time of task A, the performance end date and time of task C, and the performance end date and time of task D, which are set as search items, are obtained.

[0087] Figures 12A to 12C are diagrams showing examples of model history tables constituting a model history 3C. Figure 12A shows a model update history table 1301, Figure 12B shows a node history table 1302, and Figure 12C shows an edge history table 1303. Note that "ver" shown in the figures corresponds to the version identifier of the process model.

[0088] 12A manages the update date and time (corresponding to "update_at" in the figure) and the update reason of the process model for each version identifier of the process model. The update reason "new construction" indicates that a new process model was created. Also, the update reason "addition of new task D and equipment D" indicates that a new task D and equipment D were added to an existing process model.

[0089] Node history table 1302 shown in Fig. 12B manages node IDs, types, and node names for each version identifier of the process model. The node ID is an identifier for distinguishing business nodes and 4M data items from each other. As for type, "activity" indicates a business node, and "machine" indicates a facility node. There may also be other types indicating 4M nodes, such as "material," "man," and "method." The node name indicates the name of the node corresponding to the node ID.

[0090] The edge history table 1303 shown in FIG. 12C manages the edge ID, the input source ("From" in the figure), and the output destination ("To" in the figure) for each version identifier of the process model.

[0091] An edge ID is an identifier used to distinguish between edges between multiple business nodes and between business nodes and 4M nodes. The input source indicates the node ID of the business node or 4M node that is the start point of the directed graph. The output destination indicates the node ID of the business node or 4M node that is the end point of the directed graph.

[0092] Figures 13A to 13D are diagrams showing examples of model history tables. Figure 13A is a data item history table 1401, Figure 13B is a table history table 1402, Figure 13C is a column history table 1403, and Figure 13D is a node and data item correspondence history table 1404. Note that "ver" in the figure corresponds to the version identifier of the process model, as above.

[0093] 13A manages item IDs, item names, and references for each version identifier of a process model. The item ID is an identifier that can distinguish multiple data items from each other. The item name indicates the name of the data item. The reference indicates the table ID of the reference table name described later.

[0094] 13B manages table IDs and table names for each version identifier of a process model. The table ID indicates an identifier assigned to each table. The table name indicates the name of each table.

[0095] 13C manages column IDs, table IDs, and column names for each version identifier of a process model. The column ID is an identifier for identifying columns in each table. The table ID indicates a table having a column corresponding to the column ID. The column name indicates the name of the column corresponding to the column ID.

[0096] The node and data item correspondence history table 1404 shown in Fig. 13D manages node IDs and item IDs for each version identifier of the process model. The node ID is an identifier that can distinguish multiple business nodes or 4M nodes from each other. The item ID is an identifier that can distinguish multiple data items from each other. The node and data item correspondence history table 1404 manages the relationship with the data items of Fig. 13A that each business node or 4M node in the node history table of Fig. 12B has.

[0097] The data collection and display system 100 according to the present embodiment includes a field data storage unit 5 for storing field data, a relationship data storage unit 4 for storing a plurality of relationship data that are data for managing relationships between tasks and associate task nodes corresponding to tasks with field data related to the tasks, a model history 3C as an example of a version management unit that manages version identifiers of the plurality of process models in association with model information of the plurality of process models, a model creation unit 11 as an example of a version identifier update unit that updates the version identifier managed in the model history 3C in association with model information of the updated process model each time any one of the plurality of process models is updated, a relationship data registration unit 12 that registers relationship data based on a process model corresponding to a specific version identifier from among the plurality of process models, a model search unit 14 that searches the model history 3C using a version identifier or date and time corresponding to the updated process model as a search key, and searches the plurality of process models for model information matching the search key, and a provided data generation unit 16 that identifies the task and field data related to the task from the relationship data related to the process model corresponding to the model information, and provides the task to an outside party.

[0098] The data collection and display method of the data collection and display system according to the present embodiment includes a field data storage step in which field data is stored in a field data storage unit 5; a relationship data storage step in which a plurality of relationship data, which is data for managing relationships between tasks and associates a task node corresponding to a task with the field data related to the task, is stored in a relationship data storage unit 4; a version management step in which, using a model history 3C, a model creation unit 11, which is an example of a version identifier update unit, updates a version identifier managed in the model history 3C in correspondence with model information of the updated process model each time any one of the plurality of process models is updated; a relationship data registration step in which, from among the plurality of process models, a process model corresponding to a specific version identifier is registered; a model information search step in which a model search unit 14 searches the model history 3C using a version identifier or date and time corresponding to the updated process model as a search key, and searches the plurality of process models for model information matching the search key; and a provided data generation step in which a provided data generation unit 16 identifies the task and the field data related to the task from the relationship data related to the process model corresponding to the model information, and provides the task to an outside.

[0099] For example, when a product is defective, it is necessary to understand the on-site data on the business process in which the product was manufactured and how each task constituting the business process was performed, and to investigate the cause. In this case, the cause cannot necessarily be identified by analyzing only the on-site data of the defective product, and it is necessary to perform the analysis while comparing it with the on-site data related to the previous and next products. However, the process model at the time of manufacturing the defective product and the process model at the time of manufacturing the previous and next products are not necessarily the same. The data collection and display system 100 according to the embodiment separates the search conditions for the process model and the search conditions for the on-site data, and can reduce the effort required to identify the on-site data even when the product is defective under a situation where the process model is updated sequentially.

[0100] The data collection and display system 100 according to this embodiment includes a model data storage unit 3 including an editing model 3B that manages a process model that has started updating and is currently being updated among a plurality of process models, a latest version model 3A that manages the latest version of the process model after the update of the editing model 3B is completed, and a model history 3C. In this way, the update state of the process model to be updated can be accurately managed using the model history 3C.

[0101] In this embodiment, when the model creation unit 11 starts updating a process model to be updated among a plurality of process models, the model creation unit 11 sets the process model to be updated as the model being edited 3B. After that, when the model creation unit 11 completes updating the process model to be updated, the model creation unit 11 sets the process model to be updated (i.e., the process model of the model being edited 3B) as the latest model 3A. In this way, the model history 3C can be used to accurately manage the update state of the process model to be updated by the model creation unit 11.

[0102] In this embodiment, the model history 3C as an example of a version management unit manages the version identifier of the process model and the update date and time of the process model corresponding to the version identifier, and the model search unit 14 displays a search screen for process models and site data including at least a process model search condition field 1001 as an example of an input field for searching for an updated process model by specifying a date and time, as a search condition for the updated process model. In this way, even if the version identifier of the process model is not specified, it is possible to identify the process model that was valid at the relevant date and time, and it is possible to search for site data using the identified process model.

[0103] In this embodiment, the model search unit 14 displays, as a part of the process model and site data search screen, a process model display field 1003 that visually displays the process model corresponding to the version identifier or date and time input in the process model search condition field 1001, accepts the selection of a part of the business nodes of the process model displayed in the process model display field 1003, and displays a trace start point search condition field 1004 in which search conditions of a trace start point that traces site data for the part of the process model that has accepted the selection can be input. In this way, it becomes possible to grasp the site data identified based on the model information of the updated process model, without specifying the date and time or the version identifier, respectively, as search conditions for the updated process model.

[0104] (2) Modifications of this embodiment Fig. 14 is a diagram showing an example of a search sequence for relational data and site data according to a modified example of this embodiment. The search sequence for relational data and site data shown in Fig. 14 is almost the same as the search sequence for relational data and site data shown in Fig. 9, so the following description will focus on the differences.

[0105] 3, the site data management information 370 manages the configuration information of the site data stored in the site data accumulation unit 5. The process model is also updated when the site data management information 370 is changed. In this case, the site data having the configuration information before the change does not exist after the change, so an acquisition error may occur when attempting to acquire the current site data from the site data accumulation unit 5 based on the site data management information of the past process model searched based on the search conditions of the process model.

[0106] For example, suppose the columns in the equipment C table were "Product ID", "Set value", and "Measured value". In this case, suppose that measured values ​​obtained from equipment C are added, and as a result, the columns in the equipment C table change to "Product ID", "Set value", "Measured value 1", and "Measured value 2". In this case, even if you try to obtain field data for the "Measured value" column from the equipment C table based on the process model before the change, a data acquisition error will occur because the "Measured value" column does not exist in the current equipment C table.

[0107] In a modified example of this embodiment, the model history 3C manages the site data management information of the site data storage unit 5 as the model information of the process model. The model search unit 14 acquires information in the latest version of the process model for the management information of the site data among the components of the process model, and acquires the site data based on the management information of the site data in the latest version of the process model. Alternatively, the model search unit 14 acquires the latest version of the process model based on the latest version of the model, and as a result of the search based on the version identifier of the process model or the search date and time, changes the site data management information among the model information of the acquired process model to the site data management information of the latest version of the process model, and acquires the site data based on the site data management information of the latest version of the process model. A specific description will be given below.

[0108] The relationship data and site data search sequence shown in FIG. 14 is different from the relationship data and site data search sequence shown in FIG. 9 in that steps S904a and S904b are added.

[0109] In a modified example of this embodiment, even when searching for site data based on an old version of a process model, the site data is searched for using the latest process model information for management information of the site data, such as tables and columns related to the site data.

[0110] Specifically, in the search sequence of the association data and the site data shown in FIG. 14, in step S904, the model search unit 14 acquires information of the corresponding process model from the model history 3C based on the search conditions of the process model, as in FIG. 9. Then, in step S904a, the model search unit 14 searches the model history 3C for management information of the site data such as a table or a column corresponding to the latest version of the process model. In step S904b, the management information of the latest site data is responded as a model response. In step S905a, the model search unit 14 responds to the provided data generation unit 16 with the management information of the latest site data via the model search interface 13 as a model response. In step S908, the provided data generation unit 16 searches for the site data using the management information of the latest site data acquired here. Since the subsequent steps S906 to S911 are the same as the steps S906 to S911 shown in FIG. 9, the description will be omitted.

[0111] (3) Other modifications In this embodiment, three types of worker data generating devices 6a, a facility / machine data generating device 6b, and a part / product data generating device 6c are exemplified as the data generating devices 6, but the present invention is not limited to this, and other data generating devices may be exemplified.

[0112] In this embodiment, the process model 300 is exemplified as shown in FIG. 3, but the present invention is not limited to this and may have other forms. [Industrial Applicability]

[0113] The present invention can be applied to a data collection and display system that collects on-site data from on-site data generating devices installed in production facilities of a factory. [Explanation of symbols]

[0114] 1...information system, 2...network, 3...data model storage unit, 4...relationship data storage unit, 5...field data storage unit, 6...data generating device, 6A...data generating device, 6B...data generating device, 6C...data generating device.

Claims

1. a site data storage unit for storing site data; an association data storage unit for storing a plurality of association data for managing associations between tasks, the association data storing unit storing a plurality of association data for associating a task node corresponding to the task with the on-site data related to the task; a version management unit that manages version identifiers of the plurality of process models in association with model information of the plurality of process models; a version identifier update unit that updates the version identifier managed in the version management unit in correspondence with model information of the updated process model every time any one of the plurality of process models is updated; a correlation data registration unit that registers correlation data based on a process model corresponding to a specific version identifier from among the plurality of process models; a model information search unit that searches the version management unit using the version identifier or date and time corresponding to the updated process model as a search key, and searches the plurality of process models for model information matching the search key; a provision data generation unit that identifies the business and the on-site data related to the business from association data related to a process model corresponding to the model information and provides the business and the on-site data related to the business to an outside; A data collection and display system comprising:

2. an editing model for managing a process model that has started updating and is currently being updated among the plurality of process models; a latest version model for managing the latest version of the process model after the update of the model being edited is completed; A model history as the version control unit; A model data storage unit including:

2. The data collection and display system of claim 1.

3. the version management unit manages a version identifier of the process model and an update date and time of the process model corresponding to the version identifier; The model information search unit displaying a screen including an input field for inputting at least the version identifier or a search date and time corresponding to the updated process model as a search condition for the updated process model; 2. The data collection and display system of claim 1.

4. The model information search unit displaying, as a part of the screen, a process model display field visually representing the process model corresponding to the version identifier or search date and time input in the input field, accepting a selection of a part of a business node of the process model displayed in the process model display field, and displaying a trace start search condition field in which a search condition of a trace start point for tracing the on-site data for the part of the process model for which the selection has been accepted can be input; 4. The data collection and display system of claim 3.

5. The version management unit managing on-site data management information of the on-site data storage unit as model information of the process model; The model information search unit Obtaining an updated process model based on the updated model; changing the on-site data management information of the process model among the model information of the process model acquired as a result of the search based on the version identifier of the process model or the search date and time to the on-site data management information of the latest version of the process model; Acquire on-site data based on on-site data management information of the latest version of the process model 3. The data collection and display system of claim 2.

6. A data collection and display method for a data collection and display system that collects on-site data, comprising: a site data storage step in which the site data is stored in a site data storage unit; an association data storage step in which a plurality of association data for managing associations between tasks, the association data relating to a task node corresponding to the task and the on-site data related to the task, are stored in an association data storage unit; a version management step of managing version identifiers of the plurality of process models in association with model information of the plurality of process models using a version management unit; a version identifier updating step of updating the version identifier managed in the version management unit in correspondence with model information of the updated process model by a version identifier updating unit, every time the version identifier updating unit updates any one of the plurality of process models; a correlation data registration step of registering correlation data based on model information of a process model corresponding to a specific version identifier from among the plurality of process models; a model information retrieval step in which a model retrieval unit searches the version management unit using the version identifier or date and time corresponding to the updated process model as a search key, and retrieves model information matching the search key from the plurality of process models; a provision data generation step in which a provision data generation unit identifies the business and on-site data related to the business from relational data related to a process model corresponding to the model information, and provides the business and on-site data related to the business to an outside; 13. A data collection and display method comprising:

Images