Process model management system and process model management method

The process model management system synchronizes performance and master data to generate consistent combined models, addressing inconsistencies and improving productivity in manufacturing data analysis.

JP7781095B2Active Publication Date: 2025-12-05HITACHI LTD
View PDF 11 Cites 0 Cited by

Patent Information

Application Number
JP2023035800
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2023-03-08
Publication Date
2025-12-05
Estimated Expiration
2043-03-08

AI Technical Summary

Technical Problem

Inconsistent data between on-site work processes and process models leads to errors and delays in data analysis, reducing productivity in manufacturing environments.

Method used

A process model management system that compares performance data and master data to generate and synchronize combined process models, detecting and addressing differences to ensure data consistency.

Benefits of technology

Enhances productivity by maintaining data consistency across manufacturing sites, facilitating accurate data analysis and reducing errors.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007781095000001
    Figure 0007781095000001
  • Figure 0007781095000002
    Figure 0007781095000002
  • Figure 0007781095000003
    Figure 0007781095000003
Patent Text Reader

Abstract

To efficiently manage a process model.SOLUTION: A process model management system includes a processor and a storage device. The storage device holds operation performance data of a manufacturing site, and master data including operation design information. The processor generates a performance process model on the basis of the performance data, generates a master process model on the basis of the master data, generates a synthetic process model obtained by synthesizing the performance process model with the master process model, detects difference of the performance process model by a change in the performance data in the case that there is the change in the performance data, detects difference of the master process model by a change in the master data in the case that there is the change in the master data, detects difference of the synthetic process model by the change in the performance data or the master data, and outputs notification based on the detected difference.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a technique for managing a process model. [Background technology]

[0002] In the manufacturing industry, manufacturing processes are sometimes modeled and on-site data is managed by associating it with the model (i.e., a process model). Patent Document 1 discloses, for example, Japanese Patent Application Laid-Open No. 2019-153051 (Patent Document 1). Patent Document 1 states, "An information collection and display system in which a data generating device that generates on-site data and a transaction data storage unit that stores the on-site data are connected, includes: an on-site data storage unit that stores on-site data association data that defines the association between each of a plurality of pieces of information included in the on-site data; an on-site data search unit that searches for second information related to first information included in the plurality of pieces of information based on the association data; and a user interface that displays the connections between the plurality of pieces of information associated by the association data, wherein the on-site data search unit searches for second information related to the first information displayed on the user interface and displays the first information and the second information together with the connections between the plurality of pieces of information on the user interface."

[0003] Furthermore, as a technology for analyzing business processes, for example, Japanese Patent Application Laid-Open No. 2020-126301 (Patent Document 2) discloses, in which it is stated that "the CPU of the business process analysis device generates a current business process based on predetermined work information related to the current work of the target business process input by user operation, extracts differences between the generated current business process and a business process model corresponding to the current business process that has been prepared in advance, and displays multiple improvement plans for reducing the extracted differences together with the differences on the display unit." [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2019-153051 [Patent Document 2] Japanese Patent Publication No. 2020-126301 Summary of the Invention [Problem to be solved by the invention]

[0005] As described above, by modeling a manufacturing process and managing on-site data in association with the process model, it becomes possible to acquire data via the process model, facilitating data analysis across the entire business process. Here, when modeling a manufacturing process, if the number of processes and the number of tasks included in the processes are large, it becomes difficult to manually construct a process model. Therefore, in some cases, the process model is automatically generated based on performance data acquired from the manufacturing site. However, in this case, for example, if the on-site work process is changed, the performance data acquired from the site may no longer be consistent with the process model, and it may become impossible to acquire specific data via the process model.

[0006] On the other hand, a process model can also be generated based on the master data created when the process is designed. However, even in this case, changes to the on-site work process can cause the performance data acquired from the on-site to become inconsistent with the process model. Furthermore, if the master data is changed but the on-site does not respond, an inconsistency between the performance data and the process model can occur.

[0007] If the process model becomes inconsistent with the actual conditions on-site as described above, it becomes impossible to obtain appropriate data through the process model, which leads to errors and delays in data analysis, resulting in reduced productivity.

[0008] The present invention aims to improve productivity by managing and updating performance data and master data, thereby enabling data acquisition from a process model that is consistent with the manufacturing site. [Means for solving the problem]

[0009] In order to solve at least one of the above problems, the present invention provides a process model management system having a processor and a storage device, wherein the storage device holds performance data indicating the performance of tasks executed at a manufacturing site and master data including design information on the order of tasks to be executed, the processor generates a performance process model including information on the order of tasks execution based on the performance data, generates a master process model including information on the order of tasks execution based on the master data, and generates a combined process model including both the information on the order of tasks execution included in the performance process model and the information on the order of tasks execution included in the master process model, and when there is a change in the performance data, a previous process model generated based on the performance data before the change is generated. The system detects a difference between the actual process model and a new actual process model generated based on the actual data after the change, and when there is a change in the master data, detects a difference between the past master process model generated based on the master data before the change and the new master process model generated based on the master data after the change, detects a difference between the past combined process model generated based on the actual process model and the master process model before the actual data and the master data were changed, and a new combined process model generated based on the actual process model and the master process model after one of the actual data and the master data is changed, and outputs a notification based on the detected difference. [Effects of the Invention]

[0010] According to one aspect of the present invention, productivity can be improved by efficiently managing process models.

[0011] Problems, configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a block diagram showing an overview of a process model management technique according to an embodiment of the present invention; [Figure 2A] 1 is a block diagram showing an example of a configuration of a process model management system according to an embodiment of the present invention; [Figure 2B] 1 is a block diagram showing an example of a hardware configuration of a computer system for realizing a process model management system according to an embodiment of the present invention. [Figure 3] FIG. 2 is a block diagram showing an example of a configuration of a process model management unit according to an embodiment of the present invention. [Figure 4] FIG. 2 is an explanatory diagram illustrating an example of data stored in a performance data storage unit of the process model management system according to an embodiment of the present invention. [Figure 5] FIG. 2 is an explanatory diagram illustrating an example of data stored in a master data storage unit of the process model management system according to an embodiment of the present invention. [Figure 6] FIG. 2 is an explanatory diagram illustrating an example of a process in which the process model management system according to the embodiment of the present invention generates an achievement process model based on achievement data. [Figure 7] FIG. 10 is an explanatory diagram illustrating an example of a process in which the process model management system according to the embodiment of the present invention generates a master process model based on master data. [Figure 8A] 1 is a flowchart illustrating an example of processing executed by a process model management unit of a process model management system according to an embodiment of the present invention. [Figure 8B] 1 is a flowchart illustrating an example of processing executed by a process model management unit of a process model management system according to an embodiment of the present invention. [Figure 8C] 1 is a flowchart illustrating an example of processing executed by a process model management unit of a process model management system according to an embodiment of the present invention. [Figure 9] FIG. 2 is an explanatory diagram illustrating an example of processing executed by a process model management unit of the process model management system according to the embodiment of the present invention. [Figure 10]FIG. 10 is an explanatory diagram showing an example of a screen displayed when an actual process model is changed and synchronized with a master process model in the process model management system according to the embodiment of the present invention; [Figure 11A] FIG. 10 is an explanatory diagram showing an example of a screen displayed when an actual process model deviates from a master process model due to a change in the actual process model in the process model management system according to the embodiment of the present invention; [Figure 11B] FIG. 10 is an explanatory diagram showing an example of a screen displayed when an actual process model deviates from a master process model due to a change in the actual process model in the process model management system according to the embodiment of the present invention; [Figure 12] FIG. 10 is an explanatory diagram showing an example of a screen displayed when a master process model is changed and synchronized with an actual process model in the process model management system according to the embodiment of the present invention; [Figure 13] FIG. 10 is an explanatory diagram showing an example of a screen displayed when a master process model deviates from an actual process model due to a change in the master process model in the process model management system according to the embodiment of the present invention; DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[0014] FIG. 1 is a block diagram showing an overview of a process model management technique according to an embodiment of the present invention.

[0015] In this embodiment, management of a process model that models the manufacturing process of a product at the manufacturing site 120 will be described.

[0016] The computer 100 generates a master process model based on the master data input by the master data manager 110 (step 101). The master data is design information for the manufacturing process managed by the master data manager 110, and includes, for example, information defining the execution order of the tasks that make up each process and the execution order of the processes. A process model generated based on the master data is referred to as a master process model. Examples of master data and master process models will be described later.

[0017] When the master administrator changes the master data, the master process model generated based on that change is also changed. The computer 100 compares the newly generated master process model with the previously generated master process model and detects any differences between them (step 102).

[0018] Furthermore, the computer 100 generates an actual process model based on the performance data acquired from the manufacturing site 120 (step 103). The performance data is information on each task in each process of product manufacturing that was actually performed at the manufacturing site 120, and includes, for example, information on the time when each task in each process was actually performed for each product, and the relationship between the processes. A process model generated based on the performance data is referred to as an actual process model. Examples of performance data and actual process models will be described later.

[0019] When the actual manufacturing process (hereinafter also referred to as the on-site process) at the manufacturing site 120 is changed, the performance data changes accordingly, and as a result, the generated performance process model also changes. The computer 100 compares the newly generated performance process model with a previously generated performance process model, and detects any differences between them (step 104).

[0020] The computer 100 then compares the actual process model with the master process model, detects any differences between them (step 105), and generates a composite process model based on the detected differences (step 106).The computer 100 then compares the newly generated composite process model with a previously generated composite process model, detects any differences between them, and notifies the process model manager 130 of the results.

[0021] Based on the notified differences in the composite process model, the process model manager 130 recommends changes to the master data to the master data manager 110 and changes to the on-site process to the manufacturing site, as necessary.

[0022] FIG. 2A is a block diagram showing an example of the configuration of a process model management system according to an embodiment of the present invention.

[0023] The process model management system 200 of this embodiment is used by an enterprise 210 that operates a product manufacturing business at a manufacturing site 120. The process model management system 200 shown in Fig. 2 includes a process model management unit 211, an information collection unit 212, a master data storage unit 213, a performance data accumulation unit 214, a performance process model accumulation unit 215, a master process model accumulation unit 216, a composite process model accumulation unit 217, a master data management terminal 219, a process model management terminal 221, a manufacturing site management terminal 231, and a work performance data generation device 232.

[0024] The manufacturing site management terminal 231 is a terminal used by a manager or the like of the manufacturing site 120, and may receive notifications (e.g., recommendations, which will be described later) from the system of the business operator 210 and display them to the manager or the like of the manufacturing site 120. The work performance data generating device 232 generates data (referred to as performance data in this embodiment) indicating the performance of each task in each process at the manufacturing site 120. The manufacturing site management terminal 231 and the work performance data generating device 232 may be installed at the manufacturing site, and for example, the work performance data generating device 232 may be installed for each piece of equipment that performs the tasks of a process.

[0025] The information collection unit 212 collects performance data from the work performance data generation device 232 and master data from the master data management terminal 219, and stores them in the performance data accumulation unit 214 and the master data storage unit 213, respectively. The master data management terminal 219 is a terminal used by the master data manager 110. For example, the master data manager 110 can input master data by operating the master data management terminal 219.

[0026] The process model management unit 211 generates a master process model based on the master data stored in the master data storage unit 213, and stores it in the master process model accumulation unit 216. The process model management unit 211 also generates an actual process model based on the performance data stored in the performance data accumulation unit 214, and stores it in the actual process model accumulation unit 215. Then, the process model management unit 211 detects the difference between the master process model and the actual process model, generates a combined process model, stores it in the combined process model accumulation unit 217, and transmits the result to the process model management terminal 221.

[0027] The process model management terminal 221 is a terminal used by the process model manager 130 , and for example, the processing results of the process model management unit 211 are presented to the process model manager 130 via the process model management terminal 221 .

[0028] FIG. 2B is a block diagram showing an example of the hardware configuration of a computer system for realizing the process model management system 200 according to an embodiment of the present invention.

[0029] 1 and 2A is configured by, for example, a computer system 250. For example, the process model management unit 211, information collection unit 212, master data storage unit 213, performance data accumulation unit 214, performance process model accumulation unit 215, master process model accumulation unit 216, and combined process model accumulation unit 217 shown in Fig. 2A correspond to the computer 100 shown in Fig. 1, which may be realized by the computer system 250 shown in Fig. 2B.

[0030] The computer system 250 includes a processor 251, a memory (main storage device) 252, an auxiliary storage device 253, an output device 254, an input device 255, and a communication interface (I / F) 256. The above components are connected to each other by a bus. The memory 252 and the auxiliary storage device 253 are storage devices that store programs and data used by the processor 251.

[0031] The memory 252 is configured, for example, by a semiconductor memory, and is mainly used to hold programs and data currently being executed. The processor 251 executes various processes in accordance with the programs stored in the memory 252. The processor 251 operates in accordance with the programs to realize various functional units (see FIG. 2A, etc.).

[0032] The auxiliary storage device 253 is configured with a large-capacity storage device such as a hard disk drive or a solid state drive, and is used to store programs and data for a long period of time. For example, the master data storage unit 213, the performance data accumulation unit 214, the performance process model accumulation unit 215, the master process model accumulation unit 216, and the combined process model accumulation unit 217 are realized by the storage areas of the auxiliary storage device 253.

[0033] Processor 251 may be comprised of a single processing unit or multiple processing units and may include single or multiple arithmetic units or multiple processing cores. Processor 251 may be implemented as one or more central processing units, microprocessors, microcomputers, microcontrollers, digital signal processors, state machines, logic circuits, graphics processing units, systems on a chip, and / or any device that manipulates signals based on control instructions.

[0034] The programs and data stored in the auxiliary storage device 253 are loaded into the memory 252 at the time of startup or when necessary, and the programs are executed by the processor 251, thereby performing various processes of the computer system 250. Therefore, in the following description, the processes executed by, for example, the process model management unit 211 and the information collection unit 212 are processes executed by the processor 251 in accordance with the programs and controlling each unit in the computer system 250 as necessary. The same applies to the processes executed by each unit in the process model management unit 211, which will be described later with reference to FIG. 3.

[0035] The input device 255 is a hardware device through which a user inputs instructions and information. The output device 254 is a hardware device that presents various images for input and output, such as a display device or a printing device. The communication I / F 256 is an interface for connection to a network.

[0036] The computer system 250 may include two or more processors 251. The functions of the system of this embodiment may be implemented in multiple computer systems 250. In this case, the multiple computer systems 250 communicate with each other via a network. For example, some of the functions of the system of this embodiment may be implemented in one computer system 250, and other parts may be implemented in other computer systems.

[0037] FIG. 3 is a block diagram showing an example of the configuration of the process model management unit 211 according to an embodiment of the present invention.

[0038] The process model management unit 211 includes a master process model generation unit 301, a master process model difference detection unit 302, an actual process model generation unit 303, an actual process model difference detection unit 304, a difference detection unit 305 between the actual process model and the master process model, a combined process model generation unit 306, and a combined process model difference detection unit 307.

[0039] The master process model generation unit 301 generates a master process model based on the master data stored in the master data storage unit 213 and stores it in the master process model accumulation unit 216. This corresponds to step 101 in Fig. 1. Similarly, the processing of each unit will be explained below in association with the steps in Fig. 1.

[0040] The master process model difference detection unit 302 detects the difference between the newly generated master process model stored in the master process model storage unit 216 and the previously generated master process model, and transmits the result to the master data management terminal 219 (step 102).

[0041] The actual process model generation unit 303 generates an actual process model based on the actual data stored in the actual data storage unit 214 and stores it in the actual process model storage unit 215 (step 103). The actual process model difference detection unit 304 detects the difference between a newly generated actual process model stored in the actual process model storage unit 215 and the previously generated actual process model, and transmits the result to the manufacturing site management terminal 231 (step 104).

[0042] The actual process model / master process model difference detection unit 305 detects the difference between the actual process model stored in the actual process model storage unit 215 and the master process model stored in the master process model storage unit 216 (step 105). The composite process model generation unit 306 generates a composite process model based on the difference detected in step 105 and stores it in the composite process model storage unit 217 (step 106). The composite process model difference detection unit 307 detects the difference between the newly generated composite process model stored in the composite process model storage unit 217 and the previously generated composite process model, and transmits the result to the process model management terminal 221 (step 107).

[0043] FIG. 4 is an explanatory diagram showing an example of data stored in the performance data storage unit 214 of the process model management system 200 according to an embodiment of the present invention.

[0044] The performance data storage unit 214 shown in FIG. 4 stores arrival / completion data 400 and inter-process linkage data 420 as performance data. The arrival / completion data 400 is, for example, data in a table format consisting of multiple records, with each record corresponding to one task that was actually performed. Each record includes a product identification number 401, a task identification number 402, a task start time 403, and a task end time 404. A logical name (e.g., "product identification number"), a physical name (e.g., "prd_id"), and a data type (e.g., "VARCHAR" (variable-length character string) or "DATETIME" (date and time)) for each item are defined.

[0045] The inter-process linkage data 420 is, for example, data in a table format consisting of multiple records, with each record corresponding to an actual transfer between processes (for example, a product that has undergone work in one process being input into another process). Each record includes a work identification number 421, a part identification number 422, and a product identification number 423. A logical name, a physical name, and a data type are defined for each item.

[0046] FIG. 5 is an explanatory diagram showing an example of data stored in the master data storage unit 213 of the process model management system 200 according to an embodiment of the present invention.

[0047] 5 stores task master data 500 and process master data 520 as master data. Task master data 500 is, for example, data in a table format consisting of multiple records, with each record corresponding to one task included in one process. Each record includes a process identification number 501, a task identification number 502, and a task execution order 503. A logical name, a physical name, and a data type are defined for each item.

[0048] The process master data 520 is, for example, data in a table format consisting of multiple records, each of which indicates the relationship between processes. Each record includes a process identification number 521 and a next process 522. The logical name, physical name, and data type of each item are defined.

[0049] FIG. 6 is an explanatory diagram showing an example of a process in which the process model management system 200 according to the embodiment of the present invention generates an actual process model based on actual data.

[0050] Referring to FIG. 6, an example of the processing executed by the performance process model generating unit 303 in step 103 of FIG. 1 will be shown.

[0051] Arrival / completion data 600 shown in FIG. 6 shows specific examples of values ​​of each item in the arrival / completion data 400 shown in FIG. 4. This example shows that "Task 1" to "Task 4" were performed sequentially for "Product 1", and then "Task 5" and "Task 6" were performed sequentially for "Product 2". Meanwhile, inter-process linked data 620 shown in FIG. 6 shows specific examples of values ​​of each item in the inter-process linked data 420 shown in FIG. 4. This example shows that "Product 1" was input into "Task 5" as a part for manufacturing "Product 2".

[0052] The actual process model generation unit 303 generates an actual process model based on the above-mentioned actual data. Specifically, based on the above-mentioned actual data, the actual process model generation unit 303 recognizes "Task 1" to "Task 4" that are executed sequentially on "Product 1" as one process (e.g., "Process A"), and recognizes "Task 5" to "Task 6" that are executed sequentially on "Product 2" as another process (e.g., "Process B"). Then, the actual process model generation unit 303 recognizes that "Product 1," which is the deliverable of "Process A," has been input into "Task 5" of "Process B" as a part for manufacturing "Product 2."

[0053] 6 is a process model recognized by the actual process model generation unit 303 based on business data, output as data in JSON (JavaScript Object Notation, JavaScript is a registered trademark) format. The actual process model 650 includes information such as: "Process A" includes "Task 1," "Task 2," "Task 3," and "Task 4," "Task 2" is executed after "Task 1," "Task 2" is executed after "Task 3," "Task 4" is executed after "Task 4," "Process B" is executed after "Task B," "Process B" includes "Task 5" and "Task 6," and "Task 6" is executed after "Task 5."

[0054] FIG. 7 is an explanatory diagram showing an example of a process in which the process model management system 200 according to the embodiment of the present invention generates a master process model based on master data.

[0055] Referring to FIG. 7, an example of the processing executed by the master process model generating unit 301 in step 101 of FIG. 1 will be shown.

[0056] The task master data 700 shown in Fig. 7 shows specific examples of values ​​for each item in the task master data 500 shown in Fig. 5. This example shows that "Process A" includes "Task 1" to "Task 4" that are executed sequentially, and "Process B" includes "Task 5" and "Task 6" that are executed sequentially. Meanwhile, the process master data 720 shown in Fig. 7 shows specific examples of values ​​for each item in the process master data 520 shown in Fig. 5. This example shows that "Process B" is executed after "Process A."

[0057] The master process model generation unit 301 generates a master process model based on the above master data. The master process model 750 shown in Fig. 7 is a process model recognized by the master process model generation unit 301 based on the task master data 700 and the process master data 720 and output as JSON format data. The master process model 750 includes information such as: "Process A" includes "Task 1," "Task 2," "Task 3," and "Task 4," "Task 2" is executed after "Task 1," "Task 2" is executed after "Task 3," "Task 4" is executed after "Task 4," "Process B" is executed after "Task 4," "Process B" includes "Task 5" and "Task 6," and "Task 6" is executed after "Task 5."

[0058] 6 and 7, the actual process model 650 generated by the actual process model generation unit 303 is the same as the master process model 750 generated by the master process model generation unit 301. In this case, in step 105 of Fig. 1, the difference detection unit 305 between the actual process model and the master process model detects that there is no difference between them.

[0059] On the other hand, for example, if a manufacturing site supervisor changes the manufacturing process based on the actual situation at the manufacturing site, the acquired performance data will change accordingly, and the performance process model will also change accordingly. Alternatively, if a master data manager changes the master data for the purpose of improving the efficiency of the manufacturing site, the master process model will also change accordingly. In such cases, a difference between the two will be detected.

[0060] 6 and 7, an actual result process model 650 and a master process model 750 are generated in JSON format. It is desirable that the formats of both are the same in order to detect the difference between them, but they do not have to be in JSON format and any other format can be adopted.

[0061] 8A to 8C are flowcharts showing an example of processing executed by the process model management unit 211 of the process model management system 200 according to an embodiment of the present invention.

[0062] 8A to 8C start, actual process model generation unit 303 has already generated an actual process model based on the actual data stored in actual data storage unit 214, and the generated actual process model is stored in actual process model storage unit 215. Similarly, master process model generation unit 301 has already generated a master process model based on the master data stored in master data storage unit 213, and the generated master process model is stored in master process model storage unit 216. Furthermore, combined process model generation unit 306 has generated a combined process model, and the generated combined process model is stored in combined process model storage unit 217.

[0063] The actual result process model generation unit 303 monitors the actual result data (step 801). Meanwhile, the master process model generation unit 301 monitors the master data (step 802). Then, the actual result process model generation unit 303 and the master process model generation unit 301 respectively determine whether there have been any changes in the actual result data and the master data (step 803).

[0064] For example, when performance data generated by the work performance data generating device 232 is newly collected by the information collecting unit 212 and stored in the performance data storage unit 214, the performance process model generating unit 303 monitors the newly stored performance data. If the newly stored performance data differs from the performance data already stored in the performance data storage unit 214, it may be determined that the performance data has been changed.

[0065] Similarly, when master data newly generated by the master data management terminal 219 is stored in the master data storage unit 213, the master process model generation unit 301 monitors the newly stored master data. If the newly stored master data differs from the master data already stored in the master data storage unit 213, it may be determined that the master data has been changed.

[0066] If it is determined that there has been a change in the actual data, the actual process model generation unit 303 generates an actual process model based on the changed actual data and stores it in the actual process model storage unit 215 (step 804). Then, the actual process model difference detection unit 304 detects the difference between the past actual process model stored in the actual process model storage unit 215 and the newly generated actual process model (step 805), and notifies the manufacturing site management terminal 231 of the details of the detected difference (step 806). For example, even if a process change occurs that is not intended by the manufacturing site supervisor due to a machine failure or the like, the supervisor can be made aware of the change based on the notification in step 806.

[0067] Next, the actual process model / master process model difference detection unit 305 detects the difference between the newly generated actual process model and the master process model (step 807). Then, the actual process model / master process model difference detection unit 305 determines whether the newly generated actual process model is synchronized with or deviated from the master process model based on the detected difference (step 808). Here, the actual process model being synchronized with the master process model means that the actual process model is consistent with the master process model. The same applies to "synchronization" in the following explanation.

[0068] For example, if the past actual process model compared in step 805 matches the master process model and the newly generated actual process model does not match the master process model, it is determined that the newly generated actual process model has deviated from the master process model. On the other hand, if the past actual process model compared in step 805 does not match the master process model and the newly generated actual process model matches the master process model, it is determined that the newly generated actual process model is synchronized with the master process model.

[0069] If it is determined that the newly generated actual process model has deviated from the master process model, the difference detection unit 305 between the actual process model and the master process model recommends changes to the master data to the master data manager 110 (step 809). For example, regarding the difference between the actual process model and the master process model, it may be recommended to change the master process model to eliminate the difference.

[0070] Next, the combined process model generation unit 306 generates a combined process model by combining the newly generated actual process model and the master process model (step 810). For example, the combined process model generation unit 306 generates a combined process model such that each step includes both the tasks included in the actual process model and the tasks included in the master process model.

[0071] The combined process model generated at this point is a candidate to replace the combined process model that has been held up until then. The combined process model that has been held up until then is maintained until it is updated in step 813, which will be described later. The same applies to steps 814 to 817, 826 to 829, and 830 to 833, which will be described later.

[0072] Next, the combined process model difference detection unit 307 detects the difference between the newly generated combined process model and the previous combined process model stored in the combined process model storage unit 217 (step 811), and notifies the process model manager 130 of the detected difference (step 812). This notification may include information indicating that the combined process model has been changed and the location of the change. Then, the combined process model difference detection unit 307 stores the newly generated combined process model in the combined process model storage unit 217, and updates the combined process model (step 813).

[0073] If it is determined in step 808 that the newly generated actual process model is synchronized with the master process model, the combined process model generation unit 306 generates a combined process model by combining the actual process model and the newly generated master process model (step 814). This generation can be performed, for example, in the same manner as in step 810.

[0074] Next, the combined process model difference detection unit 307 detects the difference between the newly generated combined process model and the combined process model previously stored in the combined process model storage unit 217 (step 815), and notifies the process model manager 130 of the detected difference (step 816). This notification may include information indicating that the combined process model has been changed and the location of the change, and may further include information indicating that the actual process model has been changed and has been synchronized with the master process model. The combined process model difference detection unit 307 then stores the newly generated combined process model in the combined process model storage unit 217, and updates the combined process model (step 817).

[0075] If it is determined in step 803 that the master data has been changed, the master process model generation unit 301 generates a master process model based on the changed master data and stores it in the master process model storage unit 216 (step 818). Then, the master process model difference detection unit 302 determines whether the process model manager 130 has approved the registration of the master process model (step 819). If the registration of the master process model has not been approved, no action is taken (step 820). Specifically, the master process model difference detection unit 302 may wait until the registration of the master process model is approved, or the process may return to steps 801 and 802.

[0076] If the registration of the master process model is approved, the master process model difference detection unit 302 detects the difference between the past master process model stored in the master process model storage unit 216 and the newly generated master process model (step 821), and notifies the master data management terminal 219 of the contents of the detected difference (step 822).

[0077] Next, the difference detection unit 305 between the actual process model and the master process model detects the difference between the actual process model and the newly generated master process model (step 823). Then, the difference detection unit 305 between the actual process model and the master process model determines whether the newly generated master process model is synchronized with or deviated from the actual process model based on the detected difference (step 824).

[0078] For example, if the past master process model compared in step 821 matches the actual process model and the newly generated master process model does not match the actual process model, it is determined that the newly generated master process model has deviated from the actual process model. On the other hand, if the past master process model compared in step 821 does not match the actual process model and the newly generated master process model matches the actual process model, it is determined that the newly generated master process model is synchronized with the actual process model.

[0079] If it is determined that the newly generated master process model has deviated from the actual process model, the difference detection unit 305 between the actual process model and the master process model recommends changes to the on-site process to the manufacturing site supervisor (step 825). For example, regarding the difference between the actual process model and the master process model, it may recommend changes to the on-site process to eliminate the difference. This recommendation is sent to, for example, the manufacturing site management terminal 231.

[0080] Next, the combined process model generation unit 306 generates a combined process model by combining the newly generated master process model and the actual process model (step 826). This generation can be performed in the same manner as in step 810, for example.

[0081] Next, the combined process model difference detection unit 307 detects the difference between the newly generated combined process model and the previous combined process model stored in the combined process model storage unit 217 (step 826), and notifies the process model manager 130 of the detected difference (step 828). This notification may include information indicating that the combined process model has been changed and the location of the change. The combined process model difference detection unit 307 then stores the newly generated combined process model in the combined process model storage unit 217, and updates the combined process model (step 829).

[0082] If it is determined in step 824 that the newly generated master process model is synchronized with the actual process model, the combined process model generation unit 306 generates a combined process model by combining the master process model and the newly generated actual process model (step 830). This generation can be performed, for example, in the same manner as in step 810.

[0083] Next, the combined process model difference detection unit 307 detects the difference between the newly generated combined process model and the combined process model previously stored in the combined process model storage unit 217 (step 831), and notifies the process model manager 130 of the detected difference (step 832). This notification may include information indicating that the combined process model has been changed and the location of the change, and may further include information indicating that the newly generated master process model has been synchronized with the actual process model. The combined process model difference detection unit 307 then stores the newly generated combined process model in the combined process model storage unit 217, and updates the combined process model (step 833).

[0084] A specific example of the processing shown in FIGS. 8A to 8C will be described with reference to FIGS. 8A to 8C and 9. FIG.

[0085] FIG. 9 is an explanatory diagram showing an example of processing executed by the process model management unit 211 of the process model management system 200 according to an embodiment of the present invention.

[0086] At the initial point in time 901, the version of the actual data is "Actual Ver. 1," and the actual process model generated based on it shows a process in which "Task A," "Task B," and "Task C" are executed in sequence. On the other hand, the version of the master data is "Master Ver. 1," and the master process model generated based on it shows a process in which "Task A," "Task B," and "Task C" are executed in sequence. At this point in time, the actual process model and the master process model are the same (i.e., there are no differences between them), and the combined process model, like them, shows a process in which "Task A," "Task B," and "Task C" are executed in sequence.

[0087] In Figure 9, "Task A," "Task B," "Task C," etc. are displayed as circular shapes with "A," "B," "C," etc., and the rectangles surrounding them indicate the processes that include those tasks.

[0088] Thereafter, at time 902, the performance data is updated to a version called "performance version 2." Such a change may occur, for example, when a site supervisor changes the manufacturing process in order to improve the efficiency of the production line. Then, in step 803, it is determined that the performance data has changed. Then, in step 804, a performance process model is generated that shows the process in which "Task A," "Task B," "Task C," and "Task D" are executed in sequence.

[0089] In this case, the difference between the actual process model is detected in step 805, and a notification is made in step 806. Then, in step 807, "Task D" added after "Task C" is detected as a difference between the actual process model and the master process model.

[0090] In this case, it is determined in step 808 that the actual process model has deviated from the master process model. Then, in step 809, a recommendation is made to the master data manager 110 to add "Task D" after "Task C" in the master data.

[0091] In step 810, a combined process model is generated that includes the sequentially executed "Task A," "Task B," "Task C," and "Task D," as well as all of the sequentially executed "Task A," "Task B," and "Task C." In step 811, the addition of "Task D" is detected as a difference, and in step 812, this difference is notified. In step 813, the combined process model is updated to the newly generated one.

[0092] Thereafter, at time 903, the master data is changed to "Master Ver. 2." This may be the result of a change made by the master data administrator in response to a recommendation made in step 809 at time 902 above. Then, in step 803, it is determined that the master data has been changed. Then, in step 818, a master process model is generated that shows the process in which "Task A," "Task B," "Task C," and "Task D" are executed in sequence.

[0093] In this case, a difference in the master process model is detected in step 821, and a notification is made in step 822. In this example, the change in the master process model causes the master process model to match the actual process model. Therefore, in step 823, it is detected that there is no difference between the actual process model and the master process model, and in step 824, it is determined that the master process model is synchronized with the actual process model.

[0094] Then, in step 830, a combined process model is generated that indicates steps in which "Task A," "Task B," "Task C," and "Task D" are executed in sequence. Because this combined process model is the same as the one generated at time point 902, step 831 detects that there are no differences, and this fact is notified in step 832. In step 833, the combined process model is updated to the newly generated one.

[0095] After that, at time 904, the master data is changed to "Master Ver. 3." This can occur, for example, when a master data administrator tries to change the manufacturing process in order to improve the efficiency of the production line. Then, in step 803, it is determined that the master data has been changed. Then, in step 818, a master process model is generated that shows the process in which "Task A," "Task B," "Task C," and "Task E" are executed in sequence.

[0096] In this case, the difference in the master process model is detected in step 821, and a notification is made in step 822. Then, in step 823, it is detected as a difference between the actual process model and the master process model that "Task D," which is executed after "Task C" in the actual process model, has been replaced by "Task E," which is executed after "Task C" in the master process model.

[0097] In this case, it is determined in step 824 that the master process model has deviated from the actual process model, and in step 825, a recommendation is made to the manufacturing site supervisor to execute "Task E" instead of "Task D" next to "Task C" in the master data.

[0098] In step 826, a composite process model is generated consisting of "Task A", "Task B", "Task C", "Task D", and "Task E", which include all of the "Task A", "Task B", "Task C", and "Task E" that are executed sequentially.

[0099] Here, the generation of the combined process model at time point 904 will be described in detail. As described above, at time point 904, the actual process model indicates a process consisting of "Task A," "Task B" (executed after "Task A"), "Task C" (executed after "Task B"), and "Task D" (executed after "Task C"). In contrast, the master process model is updated to indicate a process consisting of "Task A," "Task B" (executed after "Task A"), "Task C" (executed after "Task B"), and "Task E" (executed after "Task C").

[0100] In this case, the combined process model is generated to indicate a process that includes all of the above tasks. That is, the combined process model is updated to indicate a process consisting of "task A," "task B" (executed after "task A"), "task C" (executed after "task B"), "task D" (executed after "task C"), and "task E" (executed after "task C"). That is, in the combined process model generated at this point 904, the task following "task C" branches into "task D" and "task E."

[0101] In step 827, the addition of "Task E" to be executed next after "Task C" is detected as a difference, and this difference is notified in step 828. In step 829, the composite process model is updated to the newly generated one.

[0102] Thereafter, at time 905, the performance data is changed to "performance Ver. 3." This may be the result of, for example, the manufacturing site supervisor changing "Task D," which is to be executed after "Task C," to "Task E" in response to the recommendation made in step 825 at time 904 above. Then, in step 803, it is determined that the performance data has been changed. Then, in step 804, an performance process model is generated that shows the process in which "Task A," "Task B," "Task C," and "Task E" are executed in sequence.

[0103] In this case, a difference between the actual process model is detected in step 805, and a notification is made in step 806. Then, in step 807, it is detected that there is no difference between the actual process model and the master process model, and in step 808, it is determined that the actual process model is synchronized with the master process model.

[0104] In step 814, a process consisting of "Task A," "Task B," "Task C," and "Task E," which are executed in sequence, is generated as a combined process model. In step 815, the difference that "Task E," which is executed after "Task C," has been deleted is detected, and this difference is notified in step 816. In step 817, the combined process model is updated to the newly generated one.

[0105] Next, examples of display screens of the process model management system 200 will be described with reference to FIGS.

[0106] FIG. 10 is an explanatory diagram showing an example of a screen displayed when an actual process model is synchronized with a master process model due to a change in the actual process model in the process model management system 200 according to an embodiment of the present invention.

[0107] A display screen 1000 shown in FIG. 10 includes a process model display section 1001 , a difference display section 1002 , a process model details display section 1003 , a recommendation display section 1004 , and a recommendation approval log display section 1005 .

[0108] The process model display section 1001 displays pairs of past and new process models for each of the actual process model, master process model, and combined process model. In the process model display section 1001, "Task 1" to "Task 8" are displayed as circular symbols with the numbers "1" to "8" written on them, respectively. Furthermore, a process that includes multiple tasks is displayed as a rectangle surrounding the symbols of those tasks.

[0109] In the example of Figure 10, the past actual process model and the past master process model do not match. The past actual process model is composed of "Process A," "Process B," and "Process C." "Process A" includes "Task 1" to "Task 4," which are executed sequentially. "Process B" includes "Task 5" to "Task 6," which are executed sequentially using the deliverables of "Task 4" as components. "Process C" includes "Task 7" to "Task 8," which are executed sequentially using the deliverables of "Task 4" as components. On the other hand, the past master process model is composed of the same "Process A" and "Process B" as above, but does not include "Process C." The past combined process model is the same as the past actual process model.

[0110] The example in Figure 10 shows that "Process C" has been deleted from the actual process model. As a result, the new actual process model consists of "Process A" and "Process B" and does not include "Process C." Meanwhile, the new master process model has not been changed from the previous master process model. Therefore, the new actual process model is synchronized with the new master process model, and the new combined process model is also changed to the same one.

[0111] Information about the detected differences between the process models is displayed in the difference display section 1002. In the example of Fig. 10, the difference display section 1002 displays the date and time when the deviation of the actual process model from the master process model occurred, and the date and time when the master process model was last updated.

[0112] Furthermore, a list of differences detected in the actual process model and a list of differences detected in the combined process model are displayed in the difference display section 1002. When the process model is updated as displayed in the process model display section 1001, it is detected that "Process C" has been deleted from the actual process model (Step 805 in FIG. 8A), and furthermore, it is detected that "Process C" has been deleted from the combined process model (Step 815 in FIG. 8B), so information indicating these differences is displayed.

[0113] The process model details display section 1003 displays information showing details of the new actual process model. In the example of Fig. 10, the new actual process model displayed in the process model display section 1001, i.e., the workflow based on the actual performance in which "Task 1" to "Task 6" are executed in sequence, is displayed. Furthermore, it displays that the new actual process model is also included in past actual process models (i.e., it is an existing model), and that manufacturing based on that workflow has been carried out with a frequency of 100 products out of 200 products.

[0114] Generally, multiple types of products are manufactured at a manufacturing site, and different consistency processes may be applied for each type. Alternatively, even for the same type of product, exceptional operations may be performed, such as low-frequency sampling inspection of one in 100 products, or handling of abnormalities in manufacturing. The frequency display in the process model details display area 1003 shows such frequencies.

[0115] The recommendation display section 1004 displays recommendations for the master data manager 110 on the changes to be made to the master data (step 809 in FIG. 8B) or recommendations for the manufacturing site supervisor on the changes to the site process (step 825 in FIG. 8C). In the example of FIG. 10, the actual process model was changed, and as a result, the actual process model was synchronized with the master process model, so neither step 809 nor 825 is executed and no recommendations are displayed.

[0116] The recommendation approval log display section 1005 displays information about whether a past recommendation was approved or rejected (i.e., whether a change was made in accordance with the recommendation). Specifically, whether a past recommendation was approved or rejected, the date and time of the approval or rejection, and the reason for rejection if rejected, are displayed. Furthermore, the recommendation approval log display section 1005 may include a link for displaying content that was previously presented as a recommendation. When the link is operated, the content of the recommendation is displayed.

[0117] In the example of Figure 10, "Process C" was added to the actual process model based on performance data, and based on that it was recommended to add "Process C" to the master process model as well. However, because the frequency of occurrence of the route from "Process A" to "Process C" is low, the addition of "Process C" was rejected, and as a result, "Process C" was deleted from the actual process model and the combined process model. This shows the history of past recommendations and the responses to those recommendations.

[0118] 11A and 11B are explanatory diagrams showing an example of a screen displayed when an actual process model deviates from a master process model due to a change in the actual process model in the process model management system 200 according to an embodiment of the present invention.

[0119] A display screen 1100 shown in Fig. 11A includes a process model display section 1101, a difference display section 1102, a process model details display section 1103, a recommendation display section 1104, and a recommendation approval log display section 1105. These correspond to the process model display section 1001, the difference display section 1002, the process model details display section 1003, the recommendation display section 1004, and the recommendation approval log display section 1005 of the display screen 1000 shown in Fig. 10, respectively, but the display contents differ in some respects from those shown in Fig. 10. The differences will be explained below.

[0120] As shown in the process model display section 1101, in the example of FIG. 11A, the past performance process model, the past master process model, and the past combined process model are all consistent, and are all configured by "Process A" and "Process B."

[0121] The example in FIG. 11A shows that "Process C" has been added to the actual process model. As a result, the new actual process model now includes "Process A," "Process B," and "Process C." Meanwhile, the new master process model has not been changed from the previous master process model. Therefore, the new actual process model deviates from the new master process model, and the new combined process model is changed to include all of "Process A," "Process B," and "Process C."

[0122] A list of differences detected in the actual process model and a list of differences detected in the combined process model are displayed in the difference display section 1102. When the process model is updated as displayed in the process model display section 1101, it is detected that "Process C" has been added to the actual process model (Step 805 in FIG. 8A), and furthermore, it is detected that "Process C" has been added to the combined process model (Step 811 in FIG. 8B), so information indicating these differences is displayed.

[0123] The process model detail display section 1103 displays the new performance process model displayed in the process model display section 1001, i.e., the performance-based workflow in which "Task 1," "Task 2," "Task 3," "Task 4," "Task 5," and "Task 6" are executed in sequence, and the performance-based workflow in which "Task 1," "Task 2," "Task 3," "Task 4," "Task 7," and "Task 8" are executed in sequence.

[0124] Furthermore, information is displayed indicating that the former is included in the past performance process model (i.e., it is an existing one), while the latter is not (i.e., it is a new one). Furthermore, information is displayed indicating that production based on the former workflow was carried out with a frequency of 100 products out of 200, while production based on the latter workflow was carried out with a frequency of 10 products out of 200.

[0125] The recommendation display section 1104 displays recommendations for the master data manager 110 on the parts to be changed in the master data (step 809 in FIG. 8B) or recommendations for the manufacturing site supervisor on the parts to be changed in the site process (step 825 in FIG. 8C). In the example of FIG. 11A, since the actual performance process model has deviated from the master process model as a result of the change, step 809 is executed and a recommendation for changing the master data to eliminate the deviation is displayed.

[0126] For example, as shown in FIG. 11B, the recommendation display section 1104 may display information recommending adding a "Process C" including "Task 7" to "Task 8" that are executed sequentially after "Process A" to a master process model consisting of "Process A" including "Task 1" to "Task 4" that are executed sequentially, and then "Process B" including "Task 5" to "Task 6" that are executed sequentially after "Process A."

[0127] The recommendation display section 1104 may further include a mail send button 1106. When the user operates the mail send button 1106, the above recommendation information is sent to the master data management terminal 219.

[0128] The recommendation approval log display section 1105 may display the same content as the recommendation approval log display section 1005 .

[0129] For example, if the workflow from "Process A" to "Process B" corresponds to a normal manufacturing process, while the workflow from "Process A" to "Process C" is an exceptional process such as a low-frequency sampling inspection, actual performance data corresponding to such exceptional work is generated by actually performing the exceptional work. Then, the performance process model generation unit 303 generates an actual performance process model from "Process A" to "Process C" based on the performance data. In this case, a difference in frequency appears as shown in the process model details display unit 1103.

[0130] If the master data manager 110 determines that such exceptional tasks should also be reflected in the process model, he or she may approve the master data change recommendation. In that case, "Process C" is added to the master process model, and the master process model is synchronized with the actual process model.

[0131] On the other hand, if the master data manager 110 determines that such exceptional tasks should not be reflected in the process model, he or she can reject the master data change recommendation. In that case, as shown in Figure 10, "Process C" is deleted from the actual process model, and the actual process model is synchronized with the master process model.

[0132] FIG. 12 is an explanatory diagram showing an example of a screen displayed when the master process model is synchronized with the actual process model due to a change in the master process model in the process model management system 200 according to the embodiment of the present invention.

[0133] A display screen 1200 shown in Fig. 12 includes a process model display section 1201, a difference display section 1202, a recommendation display section 1203, and a recommendation approval log display section 1204. These correspond to the process model display section 1001, the difference display section 1002, the recommendation display section 1004, and the recommendation approval log display section 1005 of the display screen 1000 shown in Fig. 10, respectively, but the display contents differ in some respects from those shown in Fig. 10. The differences will be explained below.

[0134] 12, the past actual process model and the past master process model do not match. The past actual process model is made up of "Process A" and "Process B." On the other hand, the past master process model is made up of "Process A," "Process B," and "Process C." The past combined process model is the same as the past master process model.

[0135] The example in Figure 12 shows that "Process C" has been deleted from the master process model. As a result, the new master process model is composed of "Process A" and "Process B" and does not include "Process C." On the other hand, the new actual process model has not been changed from the previous actual process model. Therefore, the new master process model is synchronized with the new actual process model, and the new combined process model is also changed to the same one.

[0136] The difference display section 1202 displays the date and time when the master process model was synchronized with the actual process model, the date and time when the actual process model was last updated, and the period during which the actual process model and the master process model diverged.

[0137] Furthermore, when the process model is updated as displayed in the process model display section 1201, it is detected that "Process C" has been deleted from the master process model (step 821 in FIG. 8A), and furthermore, it is detected that "Process C" has been deleted from the composite process model (step 831 in FIG. 8B), and therefore information indicating the differences between them is displayed in the difference display section 1202.

[0138] In the example of FIG. 12, since the master process model is synchronized with the actual process model as a result of the change to the master process model, neither step 809 nor step 825 is executed, and no recommendations are displayed in the recommendation display section 1203.

[0139] In the example of Figure 12, "Process C" was added to the master process model based on the master data, and based on that, it was recommended to add "Process C" to the actual process model as well. However, because there was insufficient site area for adding "Process C," the addition of "Process C" was rejected, and as a result, "Process C" was deleted from the master process model and the combined process model. The history of past recommendations and responses to these recommendations is displayed in the recommendation approval log display section 1204.

[0140] FIG. 13 is an explanatory diagram showing an example of a screen displayed in the process model management system 200 according to the embodiment of the present invention when the master process model deviates from the actual process model due to a change in the master process model.

[0141] A display screen 1300 shown in Fig. 13 includes a process model display section 1301, a difference display section 1302, a recommendation display section 1303, and a recommendation approval log display section 1304. These correspond to the process model display section 1201, the difference display section 1202, the recommendation display section 1203, and the recommendation approval log display section 1204 of the display screen 1200 shown in Fig. 12, respectively, but the display contents differ in some respects from those shown in Fig. 12. The differences will be explained below.

[0142] As shown in the process model display section 1301, in the example of FIG. 13, the past performance process model, the past master process model, and the past combined process model are all consistent, and are all configured by "Process A" and "Process B."

[0143] The example in Figure 13 shows that "Process C" has been added to the master process model. As a result, the new master process model now includes "Process A," "Process B," and "Process C." On the other hand, the new actual process model has not been changed from the previous actual process model. Therefore, the new master process model deviates from the new actual process model, and the new combined process model is changed to include all of "Process A," "Process B," and "Process C."

[0144] Furthermore, when the process model is updated as displayed in the process model display section 1301, it is detected that "Process C" has been added to the master process model (step 821 in FIG. 8A), and furthermore, it is detected that "Process C" has been added to the composite process model (step 827 in FIG. 8B), and therefore information indicating the differences between them is displayed in the difference display section 1302.

[0145] Also, in the example of Figure 13, as a result of the master process model being changed, the master process model has deviated from the master process model, so step 825 is executed and the recommendation display section 1303 displays a recommendation for changing the master data to resolve the deviation.

[0146] For example, the recommendation display section 1303 may display information recommending adding "Process C" to the on-site process, adding "Task 7" and "Task 8" to "Process C," and building a line to send products completed in "Process A" to "Process C."

[0147] The recommendation display section 1303 may further include an email send button 1305. When the user operates the email send button 1305, the above recommendation information is sent to the manufacturing site management terminal 231.

[0148] The recommendation approval log display section 1304 may display the same content as the recommendation approval log display section 1204 .

[0149] For example, if the master data manager 110 adds "Process C" to the master data for the purpose of improving the efficiency of the manufacturing site, "Process C" is added to the master process model and the composite process model, and a recommendation to add "Process C" to the site process is sent to the manufacturing site supervisor.

[0150] The manufacturing site supervisor may approve the addition of "Process C" and add "Process C" to the site process. In this case, when the work of "Process C" is actually performed and the performance data of the results is acquired, "Process C" is also added to the performance process model, and the performance process model is synchronized with the master process model.

[0151] On the other hand, if the manufacturing site supervisor determines that adding "Process C" is not appropriate, for example due to a lack of factory floor space, he or she can reject the recommendation to change the site process. In that case, "Process C" is deleted from the master process model, and the master process model is synchronized with the actual process model, as shown in Figure 12.

[0152] In addition, in the composite process models displayed in the process model display sections 1001 to 1301 in Figures 10 to 13, steps and tasks based only on the actual process model, steps and tasks based only on the master process model, and steps and tasks based on both the actual process model and the master process model may each be displayed in a different manner (for example, using figures of different shapes or different colors).

[0153] For example, among the past composite process models displayed in the process model display section 1001, "Task 1" to "Task 4" in "Process A" and "Task 5" to "Task 6" in "Process B" are based on both past performance process models and past master process models. In contrast, "Task 7" to "Task 8" in "Process C" are based only on past performance process models. Therefore, these may be displayed in different ways.

[0154] On the other hand, among the past combined process models displayed in the process model display area 1201, "Task 1" to "Task 4" in "Process A" and "Task 5" to "Task 6" in "Process B" are based on both past performance process models and past master process models. In contrast, "Task 7" to "Task 8" in "Process C" are based only on past master process models. Therefore, these may be displayed in different ways.

[0155] This allows the master data manager 110 or the manufacturing site supervisor who receives the notification to easily understand which data the work of each process is derived from, which helps them to decide whether to incorporate each process and work into the process model as it is or delete it from the process model.

[0156] According to the above-described embodiment of the present invention, even if a discrepancy occurs between the process at the manufacturing site and the master data, the process is quickly synchronized, and appropriate data can be acquired based on a process model that is consistent with the site, thereby improving productivity. For example, process changes that occur at the site can be quickly reflected in the master data. Furthermore, changes in the master data can be quickly notified to the manufacturing site. Furthermore, unintended process changes at the manufacturing site, such as due to machine failure, can be quickly detected.

[0157] Furthermore, the system according to the embodiment of the present invention may be configured as follows.

[0158] (1) A process model management system, comprising a processor (e.g., processor 251) and a storage device (e.g., at least one of memory 252 and auxiliary storage device 253), wherein the storage device holds performance data (e.g., data stored in performance data storage unit 214) indicating the performance of tasks executed at a manufacturing site, and master data (e.g., data stored in master data storage unit 213) including design information on the order of tasks to be executed, and the processor generates a performance process model including information on the order of tasks based on the performance data (e.g., step 804), generates a master process model including information on the order of tasks based on the master data (e.g., step 818), and generates a combined process model including both information on the order of tasks included in the performance process model and information on the order of tasks included in the master process model (e.g., steps 810, 814, 826, 830), and when there is a change in the performance data, A difference is detected between a past actual process model generated based on actual data before the change and a new actual process model generated based on actual data after the change (e.g., step 805). If there is a change in master data, a difference is detected between a past master process model generated based on the master data before the change and a new master process model generated based on the changed master data (e.g., step 821). A difference is detected between a past combined process model generated based on the actual process model and master process model before the change in the actual data and the master data and a new combined process model generated based on the actual process model and master process model after the change in either the actual data or the master data (e.g., steps 811, 815, 827, 831). A notification based on the detected difference is output (e.g., steps 806, 809, 812, 816, 822, 825, 828, 832).

[0159] This supports efficient management of process models based on whether or not the actual process model, the master process model, and the composite process model have been changed.

[0160] (2) In (1) above, the processor outputs information indicating the details of the difference between the detected past performance process model and the new performance process model as the notification to the supervisor at the manufacturing site (for example, steps 805 and 806).

[0161] This helps the shop floor supervisor manage the shop floor process and allows the shop floor supervisor to detect any unexpected changes in the process.

[0162] (3) In the above (2), the processor determines whether the new actual process model has deviated from the master process model or has become consistent with the master process model based on the difference between the new actual process model and the master process model (e.g., step 808). If the new actual process model has deviated from the master process model, the processor outputs information indicating the content of the difference between the new actual process model and the master process model and the changes to the master data to make the model consistent with the changed actual data, as a notification to the manager of the master data (e.g., step 809). If the new actual process model has become consistent with the master process model, the processor outputs information indicating that the new actual process model has become consistent with the master process model, as a notification to the manager of the process model (e.g., step 816).

[0163] This allows any discrepancies between the state of the manufacturing site and the master data to be quickly identified, and by providing information indicating the details of the discrepancies, helps to resolve the discrepancies.

[0164] (4) In (3) above, if the new actual process model deviates from the master process model, the processor generates a new composite process model based on the new actual process model and the master process model, regardless of whether or not the process model manager approves it (e.g., step 813).

[0165] This helps to create a process model that matches the current state of the manufacturing site.

[0166] (5) In (1) above, the processor outputs information indicating the details of the detected difference between the past master process model and the new master process model as a notice to the master data administrator (for example, steps 821 and 822).

[0167] This helps the master data administrator manage the master data.

[0168] (6) In the above (5), the processor determines whether the new master process model deviates from or is consistent with the actual process model based on the difference between the new master process model and the actual process model (e.g., step 824). If the new master process model deviates from the actual process model, the processor outputs information indicating the content of the difference between the new master process model and the actual process model and the changes to the manufacturing process at the manufacturing site to make it consistent with the changed master data, as the notification to the manufacturing site supervisor (e.g., step 825). If the new master process model is consistent with the actual process model, the processor outputs information indicating that the new master process model is consistent with the actual process model, as a notification to the process model manager (e.g., step 832).

[0169] This allows any discrepancies between the state of the manufacturing site and the master data to be quickly identified, and by providing information indicating the details of the discrepancies, helps to resolve the discrepancies.

[0170] (7) In the above (6), if the new master process model deviates from the actual process model and the approval of the process model administrator is obtained (e.g., step 819: Yes), the processor generates a new composite process model based on the new master process model and the actual process model (step 829), and if the new master process model deviates from the actual process model but the approval of the process model administrator is not obtained (e.g., step 819: No), the processor does not generate a composite process model.

[0171] This supports the generation of a process model based on new master data.

[0172] (8) In the above (1), when the processor detects a difference between the past synthesized process model and the new synthesized process model, the processor outputs information notifying the manager of the process model whether the difference between the actual process model and the master process model has been detected and the details of the detected difference (e.g., steps 812, 816, 828, 832).

[0173] This allows any discrepancies between the state of the manufacturing site and the master data to be quickly identified, and by providing information indicating the details of the discrepancies, helps to resolve the discrepancies.

[0174] (9) In (1) above, the processor outputs information for displaying the past actual process model, the new actual process model, the past master process model, the new master process model, the past combined process model, and the new combined process model (for example, information displayed on the process model display units 1001, 1101, 1201, 1301).

[0175] This makes it possible to easily grasp whether there are changes in the state of the manufacturing site and the master data, and whether there is any deviation or synchronization between the two.

[0176] (10) In (9) above, the processor outputs information for displaying, in different formats, information indicating the execution order of tasks included in the composite process model that are included only in the actual process model, the execution order of tasks included only in the master process model, and the execution order of tasks included in both the actual process model and the master process model.

[0177] This makes it easy to understand the discrepancy between the state of the manufacturing site and the master data.

[0178] (11) In the above (10), the display in a different manner is at least one of display using figures of different shapes and display using different colors.

[0179] This makes it easy to understand the discrepancy between the state of the manufacturing site and the master data.

[0180] The present invention is not limited to the above-described embodiments and includes various modifications. For example, the above-described embodiments have been described in detail to provide a better understanding of the present invention, and the present invention is not necessarily limited to those including all of the described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of each embodiment with other configurations.

[0181] Furthermore, the above-described configurations, functions, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The above-described configurations, functions, etc. may also be implemented in software, with a processor interpreting and executing a program that implements each function. Information such as the programs, tables, and files that implement each function can be stored in storage devices such as nonvolatile semiconductor memory, hard disk drives, and solid-state drives (SSDs), or in computer-readable, non-transitory data storage media such as IC cards, SD cards, and DVDs.

[0182] In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and not all control lines and information lines in the product are necessarily shown. In reality, it can be considered that almost all components are interconnected. [Explanation of symbols]

[0183] 100 computers 110 Master Data Administrator 120 Manufacturing site 130 Process Model Administrator 200 Process Model Management System 210 Business Operator 211 Process Model Management Department 212 Information Gathering Department 213 Master Data Storage Department 214 Performance Data Storage Department 215 Process Model Storage Unit 216 Master Process Model Storage Unit 217 Synthesis Process Model Storage Unit 219 Master Data Management Terminal 221 Process Model Management Terminal

Claims

1. 1. A process model management system, comprising: a processor and a storage device, the storage device holds performance data indicating the performance of work performed at the manufacturing site and master data including design information on the order of the work to be performed; The processor: generating a performance process model including information on the execution sequence of the tasks based on the performance data; generating a master process model including information on the execution sequence of the business processes based on the master data; generating a combined process model that includes both the information on the execution order of the tasks included in the actual process model and the information on the execution order of the tasks included in the master process model; When the performance data is changed, a difference is detected between the past performance process model generated based on the performance data before the change and the new performance process model generated based on the performance data after the change; When the master data is changed, a difference is detected between the past master process model generated based on the master data before the change and the new master process model generated based on the master data after the change; detecting a difference between the past combined process model generated based on the actual process model and the master process model before the actual data and the master data are changed and the new combined process model generated based on the actual process model and the master process model after one of the actual data and the master data is changed; A process model management system that outputs a notification based on the detected difference.

2. 2. The process model management system according to claim 1, wherein the processor outputs, as the notification to the supervisor at the manufacturing site, information indicating the details of the detected difference between the past performance process model and the new performance process model.

3. 3. The process model management system according to claim 2, The processor: determining whether the new actual process model has deviated from the master process model or whether the new actual process model has become consistent with the master process model based on a difference between the new actual process model and the master process model; When the new performance process model deviates from the master process model, outputting information indicating the content of the difference between the new performance process model and the master process model and the portion of the master data that has been changed to make it consistent with the changed performance data as the notification to the administrator of the master data; and when the new actual process model is consistent with the master process model, outputting information indicating that the new actual process model is consistent with the master process model as the notification to the process model manager.

4. 4. The process model management system according to claim 3, wherein the processor generates the new combined process model based on the new actual process model and the master process model, regardless of whether or not an administrator of the process model approves the new combined process model, when the new actual process model deviates from the master process model.

5. 2. The process model management system according to claim 1, wherein the processor outputs information indicating the details of the detected difference between the past master process model and the new master process model as the notification to the administrator of the master data.

6. 6. The process model management system according to claim 5, The processor: determining whether the new master process model has deviated from or matched with the actual process model based on a difference between the new master process model and the actual process model; When the new master process model deviates from the actual process model, outputting information indicating the details of the difference between the new master process model and the actual process model and the changes to the manufacturing process at the manufacturing site to make it consistent with the changed master data as the notification to the manufacturing site supervisor; a process model management system that, when the new master process model is consistent with the actual process model, outputs information indicating that the new master process model is consistent with the actual process model as the notification to the process model manager.

7. 7. The process model management system according to claim 6, The processor: generating a new composite process model based on the new master process model and the actual process model if the new master process model deviates from the actual process model and approval is obtained from a process model manager; a process model management system that does not generate the synthesized process model if the new master process model deviates from the actual process model but approval is not obtained from an administrator of the process model.

8. 2. The process model management system according to claim 1, when a difference between the past synthesized process model and the new synthesized process model is detected, the processor outputs information notifying an administrator of the process model whether a difference has been detected between the actual process model or the master process model and the contents of the detected difference.

9. 2. The process model management system according to claim 1, the processor outputs information for displaying the past actual process model, the new actual process model, the past master process model, the new master process model, the past combined process model, and the new combined process model.

10. 10. The process model management system according to claim 9, the processor outputs information for displaying, in different formats, information indicating the execution order of the tasks included in the combined process model, the execution order of the tasks included only in the actual process model, the execution order of the tasks included only in the master process model, and the execution order of the tasks included in both the actual process model and the master process model.

11. 11. The process model management system according to claim 10, The process model management system is characterized in that the display in the different manner is at least one of display using graphics of different shapes and display using different colors.

12. A process model management method executed by a computer system, comprising: the computer system includes a processor and a storage device; the storage device holds performance data indicating the performance of work performed at the manufacturing site and master data including design information on the order of the work to be performed; The process model management method includes: a step of generating an achievement process model including information on the execution sequence of the tasks based on the achievement data by the processor; a step of the processor generating a master process model including information on the execution sequence of the business processes based on the master data; a step of generating a combined process model by the processor, the combined process model including both information on the execution order of the tasks included in the actual process model and information on the execution order of the tasks included in the master process model; a step in which, when the performance data is changed, the processor detects a difference between the past performance process model generated based on the performance data before the change and the new performance process model generated based on the performance data after the change; When the master data is changed, the processor detects a difference between the past master process model generated based on the master data before the change and the new master process model generated based on the master data after the change; a step in which the processor detects a difference between the past combined process model generated based on the actual process model and the master process model before the actual data and the master data are changed, and a new combined process model generated based on the actual process model and the master process model after one of the actual data and the master data is changed; and a step of outputting a notification based on the detected difference by the processor.

Citation Information

Patent Citations

  • Business / production process establishment / execution support apparatus, business / production process support method, and program

    JP2005128658A

  • Construction simulation method and apparatus

    JP2012014309A

  • Block diagram management device, block diagram management method, and program

    JP2016177668A

  • Systems and methods for adjusting a process model

    JP2018511883A

  • Information collection display system, information collection method, and information display method

    JP2019153051A