Process model creation system and method

Abstract

To provide a technique for supporting generation of a process model suitable for a task generated on a site.SOLUTION: A process model creation system creates a model for managing, in a process including a plurality of tasks, site data acquired on a site of each task, and defining a flow of the tasks in the process. The process model creation system includes: a model accumulation section that accumulates the model; a difference data creation section that creates, on the basis of the site data acquired on the site, an instance indicating a flow of actually executed tasks, and extracts differences between the instance and the model as difference data; and a model modification section that creates a modification proposal of the model on the basis of the difference data.SELECTED DRAWING: Figure 2

Description

[Technical Field]

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

[0002] At each business site in a company, data generated at the site (hereinafter also referred to as "site data") is collected upon completion of the business or the occurrence of a specific event. On-site workers analyze this site data to improve the efficiency of their work.

[0003] For example, manufacturing processes in the manufacturing industry involve a variety of tasks, and each task may be managed by a different department. When each task is managed by a different department, it can be difficult to share information between departments. One possible reason for this is that each department uses different systems for managing tasks. Therefore, each department currently analyzes on-site data collected within its own department to improve the work efficiency of its own tasks. However, to improve the work efficiency of the entire manufacturing process, collaboration between departments is essential. It is believed that collaboration between departments can be promoted by linking on-site data generated not only within a department but throughout the entire manufacturing process.

[0004] This type of issue is not unique to manufacturing sites in the manufacturing industry, but also exists in companies in various other industries, such as logistics, retail, and service, which have a series of processes consisting of multiple tasks.

[0005] Patent Document 1 discloses an information collection system including "a relationship data storage unit that stores relationship data defining the relationship between each of a plurality of pieces of information included in site data; a relationship data search unit that searches for second information related to first information included in the plurality of pieces of information based on the relationship data stored in the relationship data storage unit; and a user interface unit that displays the connection relationships between the plurality of pieces of information associated by the relationship data, wherein the relationship data search unit searches for second information related to the first information based on the relationship data in response to selection of first information in the connection relationships between the plurality of pieces of information displayed on the user interface unit, and displays the first information and the second information together with the connection relationships between the plurality of pieces of information on the user interface unit." The information collection system of Patent Document 1 manages manufacturing process information using a relationship data model that indicates the structure of the relationship data that defines the relationship between each of a plurality of pieces of information included in site data generated from operations included in a manufacturing process, and the relationship data.

[0006] Furthermore, Patent Document 2 discloses a technique for extracting differences between a defined business process model and a current business process model and proposing improvement plans.

[0007] Furthermore, Patent Document 3 proposes detecting and quantifying the difference between a model for defining how a business should proceed and information relating to the business that has been executed. [Prior art documents] [Patent documents]

[0008] [Patent Document 1] Japanese Patent Application Publication No. 2019-153051 [Patent Document 2] Japanese Patent Publication No. 2020-126301 [Patent Document 3] Japanese Patent Application Laid-Open No. 2011-81620 Summary of the Invention [Problem to be solved by the invention]

[0009] For example, when the data structure of on-site data of a manufacturing process is defined in a process model and the on-site data is managed using the process model, the on-site data that actually occurs on-site may have a data structure that differs from the data structure defined in the process model. Such on-site data cannot be managed by a predefined process model. Possible reasons for the on-site data having a data structure that differs from the data structure predefined in the process model include the occurrence of unusual work due to rework work on-site, or changes in the on-site work flow that are not reflected in the process model. However, Patent Documents 1-3 do not disclose how to create a process model that is suited to the work that actually occurs on-site.

[0010] One object of the present disclosure is to provide a technology that supports the generation of a process model that is suited to work that occurs in the field. [Means for solving the problem]

[0011] According to one aspect included in the present disclosure, a process model creation system creates a model that defines a workflow in a process that includes multiple tasks, in order to manage field data acquired at the site of each task, and the system includes: a model storage unit that stores the model; a differential data creation unit that creates an instance that shows the workflow of an actual task based on the field data acquired at the site, and extracts the difference between the instance and the model as differential data; and a model correction unit that creates a revision proposal for the model based on the differential data. [Effects of the Invention]

[0012] According to one aspect of the present disclosure, the difference between the business flow shown in an instance created based on data actually acquired on-site and the business flow shown in a pre-created model is extracted, and a revision proposal for the model is created based on the difference, making it possible to generate a process model that is suited to the business occurring on-site. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a block diagram showing an example of the configuration of a data management system to which a process model creating system is applied; [Figure 2] FIG. 1 is a block diagram showing a functional configuration of a process model creating system. [Figure 3] FIG. 10 illustrates an example of a procedure for creating and registering a schema model. [Figure 4] FIG. 10 is a diagram illustrating an example of a processing procedure for creating a result instance and creating differential data from the result instance and a schema model. [Figure 5] FIG. 10 is a diagram illustrating an example of a procedure for creating a proposed modification of a schema model from differential data and modifying the schema model. [Figure 6] 10 is a diagram illustrating an example of information included in master data registered in a master data storage unit. FIG. [Figure 7] FIG. 10 is a diagram illustrating an example of information included in plan data registered in a plan data storage unit. [Figure 8] 10 is a diagram showing an example of information included in site data registered in a site data accumulation unit 141. FIG. [Figure 9] FIG. 2 is a diagram illustrating an example of the relationship between a manufacturing process and a business in the present embodiment. [Figure 10] FIG. 1 is a diagram illustrating an example of a model of each business and manufacturing process for a manufacturing process that is made up of multiple businesses. [Figure 11] FIG. 10 is a diagram illustrating an example of a data structure of a result instance for one material for which work has been performed. [Figure 12]FIG. 10 is a diagram illustrating an example of a procedure in which the process model creating system creates a schema model. [Figure 13] FIG. 10 is a diagram illustrating an example of a procedure in which the process model creating system creates an achievement instance and difference data. [Figure 14] FIG. 14 is a diagram showing an example of a procedure for creating a business flow in step S906 of FIG. [Figure 15] FIG. 14 is a diagram showing an example of a procedure for creating a result instance by associating information related to the business with information on parts used to create a product for the business flow in step S907 of FIG. [Figure 16] FIG. 14 is a diagram illustrating an example of a procedure for creating differential data from an achievement instance and a schema model in step S908 of FIG. [Figure 17] 10A and 10B are diagrams illustrating a specific example of extraction of difference information between a product type schema model and a performance instance. [Figure 18] FIG. 10 is a diagram showing a specific example of difference data obtained by accumulating difference information. [Figure 19] 10A and 10B are diagrams illustrating specific examples of similarities of difference information accumulated in difference data. [Figure 20] FIG. 10 is a diagram illustrating an example of a schema model and a result instance when a product of type Y is created using a product of type X as a part. [Figure 21] FIG. 10 is a diagram illustrating an example of a procedure in which the process model creation system creates a proposed revision of a schema model from a schema model and difference data. [Figure 22] FIG. 10 is a diagram illustrating an example in which the schema model correction unit adds a feature to a business node added in a correction proposal that the business node is associated with a repair business. [Figure 23] FIG. 10 is a diagram illustrating an example in which the schema model correction unit adds a feature that the business node added in the correction proposal is a business node associated with a sampling inspection business. [Figure 24] FIG. 10 is a diagram showing an example of a screen that presents a proposed modification of a schema model to a user. [Figure 25]FIG. 10 is a diagram showing an example of displaying differences in a data structure that has been corrected in a proposed correction for a schema model. [Figure 26] FIG. 10 is a diagram illustrating an example of an interface that displays detailed information about the similarity between similar differences. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0015] Note that the embodiments described below do not limit the invention according to the claims, and not all of the elements and combinations thereof described in the embodiments are necessarily essential to the solution of the invention.

[0016] In this embodiment, the process model creation system is described as being applied to an information collection system that collects field data generated in each manufacturing process and / or the operations within the process in a manufacturing factory. However, a similar process creation system can also be applied to information collection systems used in processes having multiple consecutive operations or steps in any industry, such as logistics, retail, or service.

[0017] <Block diagram>

[0018] FIG. 1 is a block diagram showing an example of the configuration of a data management system to which a process model creating system is applied.

[0019] 1, a process model creation system 110 is connected to a network 120. Also connected to the network 120 are one or more data generating devices 130, one or more on-site data storage units 141, one or more master data storage units 142, one or more plan data storage units 143, a relevance data model storage unit 150, and a relevance data storage unit 160. The process model creation system 110, data generating device 130, on-site data storage unit 141, master data storage unit 142, plan data storage unit 143, relevance data model storage unit 150, and relevance data storage unit 160 are connected to an information collection system 170 via the network 120.

[0020] Furthermore, an operation terminal 180 for operating the process model creating system 110 is connected to the process model creating system 110 .

[0021] The data generating device 130 may be, for example, a barcode reader or PC (Personal Computer) that acquires the work logs of workers, or a server, or a machine that processes parts or assembles finished products, or a sensor that collects inspection information from RFIDs (Radio Frequency Identifiers) attached to parts or finished products. The site data collected or generated by these data generating devices 130 is transmitted to the site data accumulation unit 141 via the network 120.

[0022] The on-site data accumulation unit 141 is, for example, a storage device such as a server or a memory, and accumulates the on-site data acquired by the data generating device 130.

[0023] The relevance data model accumulation unit 150 is, for example, a storage device such as a server or memory, and accumulates a model that defines the workflow of a process. This model is also referred to as a relevance data model. The relevance data model determines what information is to be collected from the site data accumulation unit 141. By changing the relevance data model defined in the relevance data model accumulation unit 150, it is possible to change what site data is to be collected from the site data accumulation unit 141.

[0024] The relationship data storage unit 160 is, for example, a storage device such as a server or memory, and stores data indicating the relationship between the on-site data stored in the on-site data storage unit 141. This data is also referred to as relationship data. The relationship data indicates what kind of work flow has occurred at the site.

[0025] The information collection system 170 collects information related to the implementation of a business. The information related to the implementation of a business is, for example, an implementation record related to the implementation of the business. The implementation record related to the implementation of the business may include business information related to the implementation of the business as well as business-related information related to the business. The business-related information is, for example, one or more pieces of information such as things, people, and equipment related to the implementation of the business, and the work procedures included in the business.

[0026] Based on the data structure defined in the relationship data model acquired from the relationship data model storage unit 150 and the relationship data acquired from the relationship data storage unit 160, the information collection system 170 collects, from the site data storage unit 141, site data indicating implementation records regarding the implementation of the work included in the data structure and site data indicating implementation records regarding the implementation of the work included in the relationship data.

[0027] The business operator that owns the process model creation system 110 may be the same as the business operator that owns the information collection system 170. Furthermore, the business operator that owns the site data accumulation unit 141, the master data accumulation unit 142, and the plan data accumulation unit 143 may be the same as the business operator that owns the information collection system 170 or the business operator that owns the process model creation system 110. Furthermore, the site data accumulation unit 141, the master data accumulation unit 142, and the plan data accumulation unit 143 may be located at the manufacturing site where the data generating device 130 is located, or may be located at the business operator that owns the information collection system 170 or the business operator that owns the process model creation system 110, or may be located at either of these locations.

[0028] <System configuration>

[0029] Next, the main functions of the process model creation system 110 will be described.

[0030] The process model creation system 110 is realized on a computer that has a central processing unit (CPU) that performs overall control of the process model creation system 110, a memory device (Read Only Memory: ROM) that stores various processing programs for realizing the functions of the process model creation system 110, a primary memory device (Random Access Memory: RAM) that temporarily stores information, a non-transitory memory device such as a hard disk drive (HDD), etc., and the following functions are realized when the CPU executes the various processing programs stored in the ROM. Some or all of these programs may be installed from other devices via non-transitory storage media or communication lines, or may be stored in advance.

[0031] FIG. 2 is a block diagram showing the functional configuration of the process model creating system 110. As shown in FIG.

[0032] As shown in FIG. 2, the process model creating system 110 includes a schema model creating unit 210, an achievement instance creating unit 220, a differential data creating unit 230, and a schema model correcting unit 240.

[0033] As mentioned above, the process model creation system 110 is connected to the field data storage unit 141, the master data storage unit 142, the plan data storage unit 143, the relationship data model storage unit 150, and the relationship data storage unit 160 via the network 120.

[0034] As described above, the process model creation system 110 is connected to the operation terminal 180. The operation terminal 180 provides the user with an environment for inputting predetermined information to the schema model creation unit 210, the result instance creation unit 220, and the schema model correction unit 240.

[0035] The process model creation system 110 creates a relevance data model (hereinafter also referred to as a schema model) that indicates, by a data structure, the relevance of on-site data related to the work that constitutes the process, from the master data acquired from the master data storage unit 142 and the plan data acquired from the plan data storage unit 143. The process model creation system 110 also creates relevance data (hereinafter also referred to as a performance instance) that indicates, by a data structure, the relevance of on-site data related to the work that constitutes the process, from the on-site data acquired from the on-site data storage unit 141. The system also corrects the schema model based on the difference between the data structure of the created performance instance and the data structure of the schema model.

[0036] The schema model creation unit 210 creates a schema model from the master data registered in the master data storage unit 142 and the plan data registered in the plan data storage unit 143 , and registers the schema model in the relationship data model storage unit 150 .

[0037] The result instance creating unit 220 creates a result instance from the site data registered in the site data storage unit 141 and registers it in the relationship data storage unit 160.

[0038] The differential data creation unit 230 compares the data structure of each result instance with the data structure of the schema model for one or more result instances created by the result instance creation unit 220 and the schema model registered in the association data model storage unit 150, and creates differential data that is an accumulation of differential information.

[0039] The schema model correction unit 240 corrects the schema model based on the differential data created by the differential data creation unit 230 , and registers the corrected schema model in the relationship data model storage unit 150 .

[0040] The information collection system 170 collects field data from the field data storage unit 141 using the schema model created by the process model creation system 110 and registered in the relationship data model storage unit 150 and the performance instance registered in the relationship data storage unit 160.

[0041] <Operation procedure>

[0042] FIG. 3 is a diagram illustrating an example of a procedure for creating and registering a schema model.

[0043] A user of the process model creation system 110 uses the operation terminal 180 to instruct the process model creation system 110 to create a schema model of a desired process (Sa301). The user may also use the operation terminal 180 to specify the time interval at which the process model creation system 110 creates a schema model. In this case, the process model creation system 110 executes processing to create a schema model at each specified time interval.

[0044] Next, the process model creating system 110 acquires the master data and the plan data from the master data storage unit 142 and the plan data storage unit 143, respectively (Sa302, Sa304).

[0045] Next, the master data storage unit 142 and the plan data storage unit 143 provide the master data and the plan data, respectively, to the process model creating system 110 (Sa303, Sa305).

[0046] Next, the process model creation system 110 identifies the workflow represented in the master data and the plan data, and creates a schema model that represents the identified workflow in a data structure (Sa306).

[0047] Next, the user edits the schema model from the operation terminal 180 (Sa307). The process model creating system 110 provides a user interface for editing the schema model created in step Sa306, and the user can edit the schema model from the user interface.

[0048] Next, the process model creation system 110 provides the created and edited schema model to the relationship data model storage unit 150 (Sa308).

[0049] Next, the relationship data model storage unit 150 registers the schema model provided by the process model creating system 110 (Sa309).

[0050] Here, the process model creation system 110 may execute the plan data search (Sa304) before the master data search (Sa302), or may execute the master data search and the plan data search simultaneously. Furthermore, the process model creation system 110 may receive the plan data before receiving the master data. As long as a schema model is created based on the master data and the plan data and registered in the association data model storage unit 150, the order of the processes from step Sa301 to step Sa309 in FIG. 3 may be reversed.

[0051] FIG. 4 is a diagram showing an example of a procedure for creating a result instance and creating differential data from the result instance and a schema model.

[0052] The user uses the operation terminal 180 to instruct the process model creation system 110 to create differential data (Sb301). Alternatively, the user may use the operation terminal 180 to specify the time interval at which the process model creation system 110 creates differential data. In this case, the process model creation system 110 executes a process of creating differential data at each specified time interval.

[0053] Next, the process model creating system 110 searches the association data model storage unit 150 for a schema model related to the desired process (Sb302).

[0054] Next, the relationship data model storage unit 150 provides the schema model to the process model creation system 110 (Sb303).

[0055] Next, the process model creation system 110 searches the site data storage unit 141 for relevant site data related to the desired process (Sb304).

[0056] Next, the on-site data accumulation unit 141 provides the on-site data to the process model creation system 110 (Sb305).

[0057] Next, the process model creation system 110 identifies the workflow represented in the on-site data, and creates a performance instance that represents the identified workflow in a data structure (Sb306).

[0058] Next, the process model creating system 110 provides the created performance instance to the relationship data storage unit 160 (Sb307).

[0059] Next, the association data accumulation unit 160 registers the provided performance instance (Sb308).

[0060] Next, the process model creating system 110 extracts the difference between the created result instance and the schema model registered in the relevance data model storage unit 150, and creates difference data based on the difference (Sb309).

[0061] Note that the process model creation system 110 may execute the site data search (Sb304) before the schema model search (Sb302), or may execute the schema model search and the site data search simultaneously. The process model creation system 110 may also receive the site data before receiving the schema model. The order of the processes from step Sb301 to step Sb309 in Fig. 4 may be reversed, as long as differential data can be created from the differences between the schema model and the performance instance created from the site data.

[0062] FIG. 5 is a diagram showing an example of a procedure for creating a proposed modification of a schema model from differential data and modifying the schema model.

[0063] The user instructs the process model creation system 110 to create a proposed revision of the schema model via the operation terminal 180 (Sc301). Alternatively, the user may use the operation terminal 180 to specify the time interval at which the process model creation system 110 creates a proposed revision of the schema model. In this case, the process model creation system 110 executes a process of creating a proposed revision of the schema model at each specified time interval.

[0064] Next, the process model creating system 110 creates a proposed modification of the schema model based on the differential data (Sc302) and sends it to the operation terminal 180 (Sc303). The operation terminal 180 presents the proposed modification of the schema model to the user.

[0065] Next, the user instructs the modification of the schema model using the operation terminal 180 based on the proposed modification of the schema model presented on the operation terminal 180 (Sc305). At this time, the user may adopt the proposed modification of the schema model as is, or may modify the proposed modification of the schema model by operating the operation terminal 180 (Sc304).

[0066] Next, the process model creation system 110 provides the suggested modification of the schema model to the association data model storage unit 150 as a new schema model (Sc306).

[0067] Next, the relationship data model storage unit 150 registers the provided schema model (Sc307).

[0068] <Data Contents>

[0069] FIG. 6 is a diagram showing an example of information included in the master data registered in the master data storage unit 142. As shown in FIG.

[0070] The master data is design information that defines each operation to be performed in a factory that realizes the process of manufacturing a product through various operations.

[0071] The master data includes business information 410, business-related information 420, product type information 430, option information 440, detailed product type information 450, and the like.

[0072] The business information 410 includes a business name 412 indicating the name of the business in association with a business identifier 411 that uniquely identifies the business.

[0073] The business-related information 420 has a business-related information name 422 indicating the name of the business-related information, a business identifier 411 that uniquely identifies the business to which the business-related information relates, and the like, in correspondence with a business-related information identifier 421 that uniquely identifies the business-related information.

[0074] The product type information 430 includes a product type name 432 indicating the name of the product type in association with a product type identifier 431 that uniquely identifies the product type that indicates the type of product.

[0075] Here, the product type, which indicates the type of product, may be determined, for example, from the options that the product has. Option information 440 has an option name 442 indicating the name of the option and option content 443 indicating the content of the option, which are associated with an option identifier 441 that uniquely identifies the option. Option content 443 may contain, for example, information such as the choices that the product can make for the option.

[0076] The product type detailed information 450 includes option details 452 indicating details of options for the product type in association with a product type identifier 431 that uniquely identifies the product type. The option details 452 may include, for example, information about what selections are available for each option for the product type.

[0077] FIG. 7 is a diagram showing an example of information included in the plan data registered in the plan data accumulation unit 143.

[0078] The planning data is information that specifies the details of each of the series of operations involved in the process of manufacturing a product.

[0079] The plan data includes task sequence information 460, part product relationship information 470, and the like.

[0080] The task sequence information 460 has a product type identifier 431 that uniquely identifies the target product type, and a task sequence 462 that is information about the task sequence, in association with a task sequence identifier 461 that uniquely identifies the task sequence. The task sequence information has a sequence number, a task identifier that uniquely identifies the task to be performed in that sequence, and the like.

[0081] The part-product relation information 470 has, in association with a part-product relation identifier 471 that uniquely identifies the part-product relation, a product type identifier 431 that uniquely identifies the type of product to be created, a part type identifier 472 that is the product type identifier 431 that uniquely identifies the type of part used to create that product, and a task identifier 411 that uniquely identifies the task that uses that part.

[0082] FIG. 8 is a diagram showing an example of information included in the site data registered in the site data accumulation unit 141. As shown in FIG.

[0083] On-site data is information obtained from work actually performed on-site in the process of manufacturing a product.

[0084] The field data includes business history information 480, business-related information history information 490, and the like.

[0085] The work history information 480 includes a product identifier 481 that uniquely identifies a product, a product type identifier 431 that uniquely identifies a product type, and a work identifier 411 that uniquely identifies a work, and includes information indicating the timing when the work was performed and a part identifier 483 that uniquely identifies the part used to create the product.

[0086] The information indicating the timing of when the work was performed may indicate the timing using date and time, etc. In the example of Fig. 8, work date and time 482 is information indicating the timing of when the work was performed. Furthermore, the information indicating the timing of when the work was performed may indicate the timing using the start date and time and the end date and time of the work.

[0087] If the pre-operation part is the same as the post-operation product, product identifier 481 may be the same as part identifier 483 .

[0088] Furthermore, when a product is made using a plurality of parts, the work history information 480 may include a plurality of part identifiers 483 .

[0089] The business-related information history information 490 corresponds to a business-related information history identifier 491 that uniquely identifies the business-related information history, and includes a business-related information identifier 421 that uniquely identifies the business-related information, a product identifier 481 that uniquely identifies the product, information indicating the timing at which the business-related information was generated, and history information of the information related to the business.

[0090] The information indicating the timing of the occurrence of the work-related information may indicate the timing using date and time, etc. In the example of FIG. 8, work date and time 492 is information indicating the timing of the occurrence of the work-related information. Furthermore, the information indicating the timing of the occurrence of the work-related information may be the start date and time and the end date and time of the work to which the generated work-related information relates. Furthermore, the history information of the work-related information may be, for example, information on the worker who performed the work, information on the equipment used to perform the work, information on the work procedure for performing the work, etc. In the example of FIG. 8, work result 493 is the history information of the work-related information.

[0091] In the following description, an example will be taken in which time information is used as information included in the field data that indicates the timing at which a task was performed.

[0092] <Process configuration>

[0093] FIG. 9 is a diagram showing an example of the relationship between a manufacturing process and operations in this embodiment. A manufacturing process includes one or more operations that produce a product. In this embodiment, one operation is defined as a unit distinguished by an operation identifier 411 that uniquely identifies the operation and is included in operation information 410 in the site data. In the example of FIG. 5, process 510 includes operations 520a and 520b.

[0094] <Schema model configuration>

[0095] Fig. 10 is a diagram showing an example of a model of each business and manufacturing process for a manufacturing process that is made up of multiple businesses. Fig. 10 shows a business model that represents the business and a schema model that represents the manufacturing process.

[0096] 10, the business process model associates on-site data generated from various devices (data generating devices 130) in each business process, thereby showing how workers, machines, parts, etc. are related to a specific business process and in what work procedures. The business process model 610, for example, centers on a business process node 620 associated with the business process, and includes a parts node 630 associated with parts required to perform the business process, a business-related information node 640 associated with the workers who perform the business process, the machines used to perform the business process, and the work procedures that define the business process procedures, and a product node 650 associated with products generated from the parts in the business process.

[0097] Product node 650, which is associated with a product for the business associated with business node 620, is a part node associated with a part used in a subsequent business associated with business node 621. Part node 63, which is associated with a part for the business associated with business node 620, is a product produced in a previous business associated with business node 622. In other words, both parts and products are materials, and the material associated with part node 630 and the material associated with product node 650 have the same meaning in terms of the attributes part and product. When there is no particular distinction between parts and products, they may be collectively referred to as material nodes.

[0098] As mentioned above, the part (Material) node 630, the product (Material) node 650, and the work-related information node 640 associated with the worker (Man), equipment (Machine), work procedure (Method), etc. may be referred to as 4M information or 4M nodes. However, the work-related information is not limited to 4M information. For example, the work-related information may be 5M information that includes, in addition to the 4M information, information on measurements performed during the work. The work-related information may also be 1M to 3M information that does not include one or more pieces of 4M information. The work-related information may also include information on the quality of the product on which the work was performed. The work-related information may also include information on the environment in which the work was performed and information on the management status.

[0099] 10, the schema model represents the relationship between the business process models of each business that makes up the manufacturing process. In the schema model, the business process models of each business that makes up the manufacturing process are associated via material nodes. In the schema model 660, for example, the business process model in business node 620 and the business process model in business node 622 are associated via material node 630, and the business process model in business node 620 and the business process model in business node 621 are associated via material node 650.

[0100] <Actual instance>

[0101] FIG. 11 shows an example of the data structure of a result instance for one material for which work has been performed. The result instance represents, in a data structure, the relationship between the material and the work actually performed for that material. This result instance can be structured so that on-site data is stored in each node in the business model for each work performed on the product. The result instance can also be structured so that key information for searching for on-site data from the on-site data storage unit 141 is stored.

[0102] 11 is an example of an actual instance for product A. The actual instance 710 has a business node 721 and a business node 722, and the business node 721 is associated with a business-related information node 730. The actual instance 710 has a relationship in which the product node 742 associated with the business node 721 is a parts node associated with the business node 722. The business node 721 and the business node 722 are associated with each other via the material node 742.

[0103] The business node stores business identifier information that uniquely identifies the business performed on product A, information indicating the timing of the business, etc. The business-related information node stores worker identifier information that uniquely identifies the worker who performed the business, equipment identifier information that uniquely identifies the equipment used to perform the business, procedure identifier information that uniquely identifies the procedure for performing the business, etc.

[0104] The part node 741 associated with the part used in the first operation performed on product A stores part identifier information and the like that uniquely identifies the part used to create product A. The other material nodes store product identifier information and the like that uniquely identifies product A.

[0105] The information collection system 170 can search for and acquire business-related information associated with the product using the schema model and the performance instance. The business operations that were envisioned in advance at the design stage for manufacturing the product are defined in the schema model. Information on business operations that were actually performed but are not defined in the schema model can be obtained from the performance instance.

[0106] <Creating a schema model>

[0107] 12 is a diagram showing an example of a procedure for creating a schema model by the process model creation system 110. The procedure shown in Fig. 12 corresponds to the operation procedure from Sa302 to Sa306 of the process model creation system 110 shown in Fig. 3.

[0108] The schema model creation unit 210 acquires master data from the master data storage unit 142 and acquires plan data from the plan data storage unit 143 (S801). Here, the plan data may be selected based on the product type specified by the user.

[0109] Next, the schema model creating unit 210 creates a business node associated with each business existing in the business information 410 for the business information 410 in the master data (S802).

[0110] Next, the schema model creation unit 210 creates a business-related information node associated with each business-related information present in the business-related information 420 for the business-related information 420 in the master data, and links the created business-related information node to the business node associated with the business indicated by the business identifier 411 in the business-related information 420 (S803).

[0111] Next, the schema model creation unit 210 processes the task sequence information 460 in the plan data for each product type indicated by the product type identifier 431 present in the task sequence information 460 (S804). The task nodes associated with each task are linked via material nodes in accordance with the order indicated by the task sequence 462 in the task sequence information 460 (S805). In addition, the last task node is linked to a product node (S806). The relationship between the task nodes created in this way is called the schema flow for the product type.

[0112] Next, the schema model creation unit 210 processes the parts-product relationship information 470 in the planning data for each product type indicated by the product type identifier 431 present in the parts-product relationship information 470 (S807). The product node linked to the last business node in the schema flow for the product type indicated by the parts type identifier 432 in the parts-product relationship information 470 is linked to the business node associated with the business indicated by the business identifier 411 (S808). The links between the business nodes, business-related information nodes, and material nodes created in this way are used as a schema model.

[0113] <Creating actual instances and differential data>

[0114] FIG. 13 is a diagram showing an example of a procedure in which the process model creating system 110 creates an achievement instance and differential data.

[0115] The procedure shown in FIG. 13 corresponds to the operation procedure from Sb302 to Sb306 by the process model creating system 110 shown in FIG.

[0116] The differential data creating unit 230 acquires a schema model from the relationship data model storage unit 150 (S901).

[0117] Next, the user searches for site data for which an achievement instance is to be created via the operation terminal 180 (S902). At this time, for example, the user selects or specifies agency information or the like as the target for which an achievement instance is to be created.

[0118] The result instance creating unit 220 acquires the site data stored in the site data storage unit 141 based on the conditions input by the user via the operation terminal 180. If there is site data that meets the conditions among the site data stored in the site data storage unit 141 (YES in S903), the result instance creating unit 220 acquires the corresponding site data (S904). On the other hand, if there is no site data that meets the conditions (NO in S903), the result instance creating unit 220 ends the process of creating the result instance.

[0119] Next, the result instance creation unit 220 performs the following series of processes on the acquired site data for each product (S905). First, the result instance creation unit 220 creates a workflow that represents the flow of work performed for the product (S906). Next, the result instance creation unit 220 creates a result instance for each product from the created workflow (S907). Next, the differential data creation unit 230 extracts the differences between the schema model and the result instance, and creates differential data that indicates the extracted differences (S908).

[0120] FIG. 14 is a diagram showing an example of the procedure for creating a business flow in step S906 of FIG.

[0121] The result instance creating unit 220 first searches the work history information 480 using the product identifier 481 as a key, and searches for information on work performed for each product included in the site data (S1001). Next, the result instance creating unit 220 sorts the work nodes associated with each work in chronological order using the time information on when each work was performed as a key (S1002), and further associates the work nodes via the material nodes with which the products are associated (S1003).

[0122] Furthermore, when the task history information 480 contains, as the part identifier 483, information on a part material that is different from the product material corresponding to the product identifier 481, the result instance creation unit 220 links the task node with the material node associated with the part indicated by the part material information (S1004).The result instance creation unit 220 also creates a task flow by associating the product node of the product with the task node of the last task performed on the product (S1005).

[0123] FIG. 15 is a diagram showing an example of the procedure for creating a performance instance by associating information related to the business process with information on the parts used to create the product in step S907 of FIG.

[0124] The actual result instance creation unit 220 searches the work-related information history information 490 using the product identifier 481 as a key, and acquires information related to work performed on the product included in the site data (S1101). If there is information matching the search key (YES in S1102), the actual result instance creation unit 220 identifies, from the time information of the acquired work-related information history, a work node associated with the work to which the work-related information history is associated, among the work nodes included in the business flow (S1103), and associates the work-related information node associated with the work-related information history with that work node (S1104). On the other hand, if there is no information matching the search key (NO in S1102), the series of processes for associating related information is terminated. This results in the creation of an actual result instance for the product.

[0125] <Create differential data>

[0126] FIG. 16 is a diagram showing an example of a procedure for creating differential data from an achievement instance and a schema model in step S908 of FIG.

[0127] This process of creating differential data is performed for all business nodes included in the data structure of the result instance and all business nodes included in the schema model (S1202, S1205).

[0128] The differential data creating unit 230 extracts a model that corresponds to the product type of the product associated with the result instance from among the schema models (S1201). The extracted model is called a product type schema model.

[0129] Next, the differential data creation unit 230 checks whether the same relationships exist in the product type schema model for the relationships between the business node and the business-related information node and material node in the result instance (S1203). If the same relationships exist in the product type schema model for all the relationships of the business node (Yes in S1203), the differential data creation unit 230 determines that there is no difference between the result instance and the schema model for that business node.

[0130] If there is no identical relationship in the product type schema model for any of the relationships in the business node (No in S1203), the differential data creation unit 230 determines that there is a difference in the business node, and accumulates the relationship between the nodes in the actual instance for which there was no identical relationship in the product type schema model as differential information in the differential data (S1204).

[0131] Next, the differential data creation unit 230 checks whether the same relationships exist in the data structure of the result instance for the relationships between the business nodes and the business-related information nodes and material nodes in the product type schema model (S1206). If the same relationships exist in the data structure of the result instance for the relationships between all business nodes and the business-related information nodes and material nodes in the product type schema model (Yes in S1206), the differential data creation unit 230 determines that there are no differences for the business nodes.

[0132] If there is no identical relationship in the data structure of the actual result instance regarding the relationship between any business node in the product type schema model and the business-related information node or material node (No in S1206), the differential data creation unit 230 determines that there is a difference in the business node, and accumulates the relationship between the nodes in the product type schema model where there was no identical relationship in the data structure of the actual result instance as differential information in the differential data (S1207).

[0133] When accumulating the difference data in steps S1204 and S1207, the difference data creation unit 230 may also accumulate, as additional information about the difference, information identifying the result instance that caused the difference and product type information about the product associated with the result instance. Furthermore, if two or more differences occur simultaneously, the difference data creation unit 230 may accumulate information identifying that these differences occurred simultaneously. The information about the differences between nodes accumulated in this way becomes the difference data.

[0134] <Examples of actual instances and differential data>

[0135] FIG. 17 is a diagram showing a specific example of extraction of difference information between a product type schema model and a performance instance.

[0136] Specifically, in the product type schema model 1310, business nodes (1320a, 1320b, 1320c, 1320d, 1320e), material nodes (1330m, 1330a, 1330b, 1330c, 1330d, 1330e), and related information nodes (1340p, 1340q) are linked to one another. Meanwhile, the data structure of the result instances includes, for that schema model, result instance 1351 in which the business node 1320c does not exist, result instance 1352 in which an extra business node 1320f exists, and result instance 1353 in which the business-related information node 1340p does not exist. At this time, differential information 1361 indicating that business node 1320c does not exist in actual instance 1351, differential information 1362 indicating that business node 1320f exists as an extra node in actual instance 1352, and differential information 1363 indicating that business-related information node 1340p does not exist in actual instance 1353 are accumulated in the differential data.

[0137] <Details of differential data, similarity>

[0138] FIG. 18 is a diagram showing a specific example of difference data obtained by accumulating difference information.

[0139] 18 is a business node, a material node, or a business-related information node. Specifically, the schema model 1410 links a node A (1411), a node B (1412), and a node C (1413). In addition, in the manufacturing process represented by the schema model, products of product types X and Y are produced, and the product type schema models for both product types are equal to the schema model 1410.

[0140] In the differential data, the differential information extracted in the result instance group 1420 for type X products and the differential information extracted in the result instance group 1430 for type Y products may be organized and stored so that the number of occurrences is held for each product type for each node between which a difference occurred, as shown in the differential data table 1440. Specifically, between node A (1411) and node C (1413), no link between the nodes exists in the schema model 1410, but when an result instance occurs in which a link exists between the nodes in the result instance group 1420 for type X, the number of times that the difference occurred in type X between the nodes may be stored (1441).

[0141] The difference data may also be stored with the similarity between the accumulated difference information added thereto.

[0142] FIG. 19 is a diagram showing a specific example of the similarity of the difference information accumulated in the difference data.

[0143] As shown in the similarity diagram 1520, when one or more differences occur in the data structure of an achievement instance in the achievement instance group 1510 of type X for the schema model 1410, the number of times or probability that other differences including the difference occur for that difference may be stored as similarity. The similarity represents the degree to which a certain difference and another difference occur simultaneously.

[0144] In the similarity diagram 1420, the arrows and the fractions displayed near them indicate the number of times the difference at the tip of the arrow occurred relative to the number of times the difference at the base of the arrow occurred. Specifically, when a difference (1521) occurs in which a link from node A (1411) to node B (1412) exists in the schema model 1410 but the link does not exist in the actual instance, the number of times or probability of a difference (1522) occurring within the same instance in which a link from node A (1411) to node C (1413) does not exist in the schema model 1410 but does exist in the actual instance may be stored. This is shown by the arrow 1523 and the fractions near it.

[0145] The similarity between difference information may be stored for difference information occurring in each result instance between materials in a part-product relationship. The similarity may be the number of times or probability that materials in a part-product relationship occur at the same time in each result instance.

[0146] FIG. 20 is a diagram showing an example of a schema model and a result instance when a product of type Y is created using a product of type X as a part.

[0147] The schema model 1610 is composed of a product type schema model 1621 for type X and a product type schema model 1622 for type Y. The product type schema model 1621 includes three business nodes (1631 to 1633). The product type schema model 1622 includes two business nodes (1634, 1635). For example, when a difference occurs between a result instance group 1621A of type X and a result instance group 1622A of type Y in which a business node C (1633) does not exist in an result instance of type X, and a difference occurs simultaneously in which an extra business node F (1636) exists in an result instance of type Y, the similarity between the difference information of these two may be retained.

[0148] <Creating a revised proposal>

[0149] FIG. 21 is a diagram showing an example of a procedure in which the process model creating system 110 creates a proposed revision of a schema model from a schema model and differential data.

[0150] The procedure shown in FIG. 21 corresponds to the operation procedure from steps Sc301 to Sc303 of the process model creating system 110 shown in FIG.

[0151] The user specifies, via the operation terminal 180, conditions for selecting differences to be reflected in the proposed revision of the schema model (S1701). The conditions for selecting differences may include setting a threshold for the number of occurrences or probability of differences, and reflecting differences exceeding the threshold in the proposed revision. Alternatively, a period may be specified, and differences occurring in result instances related to products in which work related to the products was performed during a period included in the user-specified period may be selected. Alternatively, a product type may be specified, and differences occurring in result instances related to products matching the user-specified product type may be selected. Alternatively, a product option may be specified as a condition, and differences occurring in result instances related to products matching the user-specified option conditions may be selected. Multiple conditions may also be specified simultaneously. In this case, a priority may be assigned to each specified condition, and differences matching any of the conditions may be reflected in the proposed revision. When multiple different differences occur at the same location in the schema model, the difference with the higher priority may be reflected.

[0152] Next, the schema model correction unit 240 extracts difference information of differences that match specified conditions from the difference data (S1702). The extracted difference information is called reflection target difference information. The schema model correction unit 240 performs the following series of processes for each difference included in the reflection target difference information (S1703).

[0153] First, if the schema model correction unit 240 determines that the location where the difference occurs in the schema model has already been corrected using other difference information (Yes in S1704), it does not perform the correction and ends the processing for the difference information. If the location where the difference occurs has not already been corrected using other difference information (No in S1704), the schema model correction unit 240 reflects the difference in the schema model (S1705). As a result, when differences extracted under multiple conditions occur at the same location and are contradictory, the difference that matches the condition with the highest priority can be preferentially reflected in the proposed correction for the schema model.

[0154] At this time, differences whose similarity to the differences reflected in the revision plan exceeds a threshold may be added to the reflection target difference information (S1706 to S1707). This allows differences that are highly similar to the differences reflected in the revision plan to be reflected in the revision plan. The similarity threshold may be set by the user when specifying the difference reflection conditions.

[0155] <Feature addition>

[0156] When creating a proposed revision of a schema model, the schema model revision unit 240 may add information indicating the characteristics of the business corresponding to the business node added in the proposed revision, based on the difference in configuration between the schema model before revision and the proposed revision.

[0157] 22 is a diagram showing an example in which the schema model correction unit 240 adds a characteristic to a business node added in a correction proposal that the business node is associated with a repair business. A repair business is a business that improves a product created in a downstream business and returns it to an upstream business. For example, a business that performs work to resolve a defect in a product corresponds to a repair business.

[0158] The schema model 1810 includes five business nodes 1811 to 1815. As a difference between the result instance group 1820a and the schema model 1810, the result instance group 1820a has a business node 1821 that is not defined in the schema model 1810. The business node 1821 is connected downstream of the business node 1813, and is connected from the business node 1821 to the business node 1812 that has already been passed through. In the case of such a structure, the schema model correction unit 240 adds a business node corresponding to the business node 1821 and a material node corresponding to the product thereof to a position branching from the material node corresponding to the product of the business node 1813 in the schema model 1810, and creates a schema model correction proposal 1830a in which the added material node is connected to the business node 1813, and may also add a feature to the added business node that it is a business node associated with on-site repair work.

[0159] 23 is a diagram showing an example in which the schema model correction unit 240 adds a feature to a business node added in a proposed correction that the business node is associated with a sampling inspection business. A sampling inspection business is a business in which some of the products of a certain business are inspected as samples.

[0160] As a difference between the result instance group 1820b and the schema model 1810, the result instance group 1820b has a business node 1822 that is not defined in the schema model 1810. The business node 1822 is connected to a material node corresponding to the product of the business node 1814 in the schema model 1810, and the material node corresponding to the product of the business node 1822 is connected to a business node 1815 in the schema model 1810. In the case of such a structure, the schema model correction unit 240 adds a business node corresponding to the business node 1822 and a material node corresponding to the product at a position branching from the material node corresponding to the product of the business node 1814 in the schema model 1810, and creates a schema model correction proposal 1830b in which the added material node is connected to the business node 1815, and may also add to the added business node a feature that it is a business node associated with a sampling inspection job at the site.

[0161] <Screen display>

[0162] FIG. 24 is a diagram showing an example of a screen that presents a proposed modification of the schema model to the user.

[0163] The screen of the user interface 1910 in Figure 24 includes an area 1920 that displays the current schema model, an area 1930 that displays nodes whose data structure differs from the current schema model, an area 1940 that displays a proposed revision to the schema model, and an area 1950 of buttons for instructing the application of the proposed revision to the schema model as a schema model.

[0164] In the area 1920 for displaying the current schema model, the schema models registered in the relationship data model storage unit 150 are displayed.

[0165] In the area 1930 that displays the nodes where a data structure difference has occurred, one or more nodes in the proposed revision of the schema model created by the schema model revision unit 240 that have a difference from the schema model are displayed so that they can be identified.

[0166] The area 1940 displaying the proposed revision of the schema model displays the proposed revision created by the schema model revision unit 240. When the proposed revision includes a business node 1941 to which a feature has been added by the schema model revision unit 240, the business node may be displayed so as to be distinguished from other business nodes.

[0167] Furthermore, when the proposed revision of the schema model is presented to the user in the user interface 1910, details of the differences in the data structure between the current schema model and the proposed revision may also be displayed.

[0168] 25 is a diagram showing an example of displaying differences in data structure corrected in the proposed revision of a schema model. When the user selects an area 1930d that displays a node in which a data structure difference has occurred, the user interface 1910 displays the differences in data structure corrected in the proposed revision of the schema model for that node.

[0169] In the example of FIG. 25 , the user interface 1910 displays details of the difference that occurred in the node indicated by area 1930d in area 1960 that displays the details of the difference. The data structure of the revision proposal may be displayed as the details of the difference. Furthermore, if multiple different differences in data structures have occurred in the node indicated by area 1930d and one of the differences has been adopted in the revision proposal, area 1960 may display a data structure (1961) of the revision proposal of the schema model as well as a data structure (1962) of the difference that has not been adopted in the revision proposal. In area 1960, the user may be able to change the difference to be reflected in a node with a revision proposal from the data structure displayed in area 1961 to the data structure displayed in area 1962, manually change the connection between nodes, or select not to reflect the difference in the node.

[0170] Furthermore, user interface 1910 may further include area 1970 for displaying the characteristics of the product that caused the difference when displaying the details of the difference in area 1960. Area 1970 may also display the number of occurrences and occurrence probability for one or more product types for the products in which the difference occurred.

[0171] Furthermore, the user interface 1910 may further include an area 1980 that displays performance instances for one or more products that have caused the difference when displaying the details of the difference in the area 1960. When performance instances for parts used in the product or performance instances for products in which the product has been used as a part are present in the area 1980 together with the performance instance 1981 for the product in which the difference has occurred, these performance instances may also be displayed in association with the performance instance 1981.

[0172] In addition, the user interface 1910 may further include an area 1990 in area 1980 that displays information stored at each node in the actual instance when displaying the product that caused the difference and the actual instance of a part of that product or a higher-level product that uses that product as a part.

[0173] Furthermore, when the user interface 1910 displays details of the difference that occurred in the node shown in area 1930d in area 1960 that displays the details of the difference, it may display that the similarity is high in area 1930b that displays the node in which the difference that occurred in the node shown in area 1930d has occurred, the similarity exceeding a threshold. In this case, the index representing the similarity may be the probability of simultaneous occurrence, and the value thereof may be displayed.

[0174] When the area 1930b indicates a high degree of similarity, if the user selects the area 1930b, the user interface 1910 may display detailed information about the similarity between the differences that are similar to each other.

[0175] FIG. 26 is a diagram showing an example of an interface that displays detailed information about the similarity between similar differences.

[0176] 26, it is assumed that the similarity between the difference occurring in the node shown in area 1930d and the difference occurring in the node shown in area 1930b exceeds a threshold value. It is also assumed that area 1930d represents the comparison source, and area 1930b represents the comparison destination.

[0177] The user interface 1910 displays detailed information about the similarity between a difference 2011 that has occurred in the node shown in the area 1930d and a difference 2012 that has occurred in the node shown in the area 1930b.

[0178] Area 2010 displays a data structure consisting of a series of one or more actual instances, including difference 2011 and difference 2012. Here, in difference 2011, when there are differences not adopted in the proposed revision of the schema model in addition to the differences adopted in the proposed revision, it may be possible to switch the display from the data structure of the differences adopted in the proposed revision to the data structure of the differences not adopted in the proposed revision.

[0179] Furthermore, when the difference 2012 contains differences not adopted in the revision proposal in addition to differences adopted in the revision proposal, the display of the difference 2012 may be switched to the data structure of the differences not adopted in the revision proposal.

[0180] Furthermore, when displaying details of similar differences in area 2010, area 2020 may be provided that displays the characteristics of the product that caused the difference for each of difference 2011, which is the source of the similarity comparison, and difference 2012, which is the target of the comparison. Area 2020 may display the number of occurrences and occurrence probability for one or more product types for the products in which the difference occurred. Area 2020 may also have information indicating the level of similarity between difference 2011, which is the source of the similarity comparison, and difference 2012, which is the target of the comparison. The information indicating the level of similarity may be, for example, a value of the probability of simultaneous occurrence.

[0181] As explained above, according to the above-mentioned embodiment, the process model creation system 110 extracts differences between the process model that indicates the relationship between the work tasks constituting the manufacturing process and the work site data and the data structure regarding the data relationship in the work site data generated at the manufacturing site, and can create a process model that reflects highly related differences using the similarity between the differences. As a result, it is possible to prevent differences that have a causal relationship from being overlooked in the process model, and to correct the process model in accordance with the state of the site, which is expected to have effects such as more accurate collection and analysis of site data.

[0182] Furthermore, the process model creation system 110 can present the characteristics of the business associated with the business nodes added to the modified process model, which is expected to have the effect of making it easier for users to understand the process model.

[0183] In the above-described embodiment, an example was described in which a manufacturing process model was created from on-site data generated in the manufacturing process at a manufacturing site, but the process model creation system 110 is not limited to manufacturing sites and can be applied to any business type that is made up of multiple tasks and generates on-site data. For example, in the logistics or transportation industry, there are multiple steps that make up the transportation process, from receiving goods to sorting, storage, packaging, and delivery, and a transportation process model can be created from on-site data related to the transportation process in the same way as a process model at a manufacturing site.

[0184] 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 clearly explain the present invention, and are 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, and / or replace part of the configuration of each embodiment with other configurations. Furthermore, the above-described configurations, functions, processing units, etc. may be partially or entirely realized in hardware, for example, by designing them as integrated circuits.

[0185] The above-described embodiment also includes the following features, but the features included in the present embodiment are not limited to those listed below.

[0186] (Item 1) A process model creation system that creates a model that defines a workflow in a process including multiple tasks, in order to manage on-site data acquired at the site of each task, comprising: a model storage unit that stores the models; a differential data creation unit that creates an instance indicating the flow of work that was actually performed based on on-site data acquired at the site and extracts the difference between the instance and the model as differential data; a model correction unit that creates a correction proposal for the model based on the difference data; A process model creation system having: This allows the system to extract the differences between the business flow shown in an instance created based on data actually acquired on-site and the business flow shown in a pre-created model, and create a revision proposal for the model based on those differences, thereby making it possible to generate a process model that is suited to the business that occurs on-site.

[0187] (Item 2) In the process model creation system according to item 1, the difference data creation unit further calculates the number of times or frequency of occurrence of each difference and a similarity between the differences, which indicates the degree to which a certain difference and another difference occur in the same instance; The model correction unit creates a correction proposal to adopt both the first difference and the second difference if the number or frequency of the first difference exceeds a first threshold and the similarity between the first difference and the second difference exceeds a second threshold. According to this, differences that frequently occur together are adopted in the revision proposal, so that a revision proposal that allows for a balanced revision can be created.

[0188] (Item 3) 3. The process model creation system according to claim 2, the differential data creation unit further calculates a similarity representing a degree to which a difference occurring in the first instance and a difference occurring in the second instance occur at the same time when a product created by a task in a first instance is used as a component in a task in a second instance; If the difference in the first instance exceeds the first threshold and the similarity between the difference in the first instance and the difference in the second instance exceeds the second threshold, the model correction unit creates a correction proposal that adopts both the difference in the first instance and the difference in the second instance. According to this, when a product of one business is a component of another business, differences that frequently occur together in those businesses are adopted in the revision proposal, so that a revision proposal that allows for balanced revision can be created.

[0189] (Item 4) 2. The process model creation system according to claim 1, Accepts from the user the specification of the difference to be extracted from the instance or the conditions for narrowing down the instances from which the difference is to be extracted, The model correction unit identifies, from the difference data, differences extracted from instances that meet the specified conditions or differences that meet the specified conditions, and creates a correction proposal for the model based on the identified differences. This allows the creation of a revision proposal that adopts differences that meet the conditions specified by the user.

[0190] (Item 5) 5. The process model creation system according to claim 4, It accepts multiple conditions, each with a priority, and extracts differences when at least one of the conditions is met. When a difference that meets one condition conflicts with a difference that meets another condition, the model correction unit preferentially adopts the difference that meets the condition with the higher priority as the correction proposal. This allows multiple conditions to be set, and if there are conflicting conditions, the difference with the higher priority is applied, making it possible to create a revision proposal that properly reflects the user's intentions.

[0191] (Item 6) 2. The process model creation system according to claim 1, The model correction unit identifies business features to be added to the model in the correction proposal based on differences in data structure between the model and the correction proposal. According to this, the characteristics of the business to be added to the model in the revision proposal are identified based on the differences in data structure between the current model and the revision proposal, so that the characteristics of the business to be added can be easily identified.

[0192] (Item 7) 7. The process model creation system according to claim 6, When the proposed revision has a configuration that returns from a task existing in the model before revision to a task existing upstream of that task via a task added in the proposed revision, the model revision unit identifies the characteristic that the added task is a rework task that improves a product created in a downstream task and returns it to the upstream task. This makes it possible to easily identify the characteristics of the repair work.

[0193] (Item 8) 7. The process model creation system according to claim 6, The model correction unit is configured so that the correction proposal connects a first task existing in the model before the correction to a task added in the correction proposal, and connects the added task to a second task existing in the next stage of the first task existing in the model, and if an instance having the added task occurs repeatedly at a predetermined time interval, it identifies the characteristic that the added task is a sampling inspection task in which a portion of the products of a certain task is inspected as a sample. This makes it possible to easily identify the characteristics of sampling inspection work.

[0194] (Item 9) 7. The process model creation system according to claim 6, The model correction unit displays the structure of the proposed correction on a screen using nodes corresponding to the business, products, or parts, and arrows connecting the nodes along the flow of the business. This allows the revision proposal to be visually and easily grasped using the nodes and arrows.

[0195] (Item 10) 10. The process model creation system according to claim 9, The model correction unit displays, in the display of the structure of the correction proposal, nodes and / or arrows of parts to be corrected in the correction proposal in a distinguishable manner. This makes it possible to easily visually identify the corrections in the correction proposal.

[0196] (Item 11) 10. The process model creation system according to claim 9, The model correction unit displays, in the display of the structure of the correction proposal, nodes of business operations whose characteristics have been identified in the correction proposal in a visually distinguishable manner. This makes it possible to easily visually identify the tasks that have been added in the proposed revision and whose features have been identified.

[0197] (Item 12) 10. The process model creation system according to claim 9, the difference data creation unit further calculates the number of times or frequency of occurrence of each difference and a similarity between the differences, which indicates the degree to which a certain difference and another difference occur in the same instance; If the number or frequency of a first difference exceeds a first threshold and the similarity between the first difference and the second difference exceeds a second threshold, the model correction unit creates a correction proposal that incorporates the first difference and the second difference, and when a selection operation is performed on a location corresponding to the first difference in the display of the structure of the correction proposal, the model correction unit displays the location corresponding to the second difference in an identifiable manner. This makes it possible to easily grasp differences with high similarity. [Explanation of symbols]

[0198] 110...process model creation system, 120...network, 130...data generation device, 141...site data storage unit, 142...master data storage unit, 143...planning data storage unit, 150...relevance data model storage unit, 160...relevance data storage unit, 170...information collection system, 180...operation terminal, 210...schema model creation unit, 220...actual result instance creation unit, 230...differential data creation unit, 240...schema model correction unit

Claims

1. A process model creation system that creates a model that defines a workflow in a process including multiple tasks, in order to manage on-site data acquired at the site of each task, comprising: a model storage unit that stores the models; a differential data creation unit that creates an instance indicating the flow of work that has actually been performed based on on-site data acquired at the site, and extracts the difference between the instance and the model as differential data; a model correction unit that creates a correction proposal for the model based on the difference data; and the differential data creation unit extracts, from a plurality of instances, portions that are present in the instances but not in the model, or portions that are present in the model but not in the instances, as differences, and further calculates the number of times or frequency of occurrence of each difference, and a similarity between the differences that indicates the degree to which a certain difference and another difference occur in the same instance; the model correction unit creates a correction plan to adopt both the first difference and the second difference when the number or frequency of a first difference, which is a difference that occurred in any of the portions, exceeds a first threshold and the similarity between the first difference and a second difference, which is a difference that occurred in a portion different from the first difference, exceeds a second threshold; Process model creation system.

2. the differential data creation unit further calculates a similarity representing the degree to which a difference occurring in the first instance and a difference occurring in the second instance occur at the same time when a product created by a task in a first instance that is one of the plurality of instances is used as a component in a task in a second instance that is one of the plurality of instances and different from the first instance; the model correction unit creates a correction plan to adopt both the difference in the first instance and the difference in the second instance when the number or frequency of the difference in the first instance exceeds the first threshold and the similarity between the difference in the first instance and the difference in the second instance exceeds the second threshold. The process model generation system according to claim 1 .

3. A process model creation system that creates a model that defines a workflow in a process including multiple tasks, in order to manage on-site data acquired at the site of each task, comprising: a model storage unit that stores the models; a differential data creation unit that creates an instance indicating the flow of work that has actually been performed based on on-site data acquired at the site, and extracts the difference between the instance and the model as differential data; a model correction unit that creates a correction proposal for the model based on the difference data; and Accepting specification of multiple conditions, each with a priority, for narrowing down differences to be extracted from an instance or instances from which differences are to be extracted, where differences are extracted when at least one of the conditions is met; the model correction unit identifies, from the difference data, differences extracted from instances that satisfy the specified conditions or differences that satisfy the specified conditions, and when a difference that satisfies one of the conditions and a difference that satisfies another condition are contradictory, creates a correction proposal for the model by preferentially adopting the difference that satisfies the condition with the higher priority. Process model creation system.

4. A process model creation system that creates a model that defines a workflow in a process including multiple tasks, in order to manage on-site data acquired at the site of each task, comprising: a model storage unit that stores the models; a differential data creation unit that creates an instance indicating the flow of work that has actually been performed based on on-site data acquired at the site, and extracts the difference between the instance and the model as differential data; a model correction unit that creates a proposed revision of the model based on the differential data, identifies business features to be added to the model in the proposed revision based on differences in data structure between the model and the proposed revision, and displays the structure of the proposed revision on a screen using nodes corresponding to businesses, products, or parts, and arrows connecting the nodes along the flow of the business; and the differential data creation unit extracts, from a plurality of instances, portions that are present in the instances but not in the model, or portions that are present in the model but not in the instances, as differences, and further calculates the number of times or frequency of occurrence of each difference, and a similarity between the differences that indicates the degree to which a certain difference and another difference occur in the same instance; the model correction unit, when the number or frequency of a first difference, which is a difference that occurred in any of the portions, exceeds a first threshold value and the similarity between the first difference and a second difference, which is a difference that occurred in a portion different from the first difference, exceeds a second threshold value, creates a correction proposal that incorporates the first difference and the second difference, and when a selection operation is performed on a portion corresponding to the first difference in the display of the structure of the correction proposal, displays the portion corresponding to the second difference in a distinguishable manner. Process model creation system.

5. A process model creation method for creating a model that defines a workflow in a process including a plurality of tasks, in order to manage on-site data acquired at the site of each task, comprising: The computer storing said model; creating an instance showing the flow of work that was actually performed based on on-site data acquired at the site, and extracting the difference between the instance and the model as difference data; A method for performing a process to generate a proposed revision of the model based on the difference data, comprising: extracting, from a plurality of instances, portions that are present in the instances but not in the model, or portions that are present in the model but not in the instances, as differences, and further calculating the number of times or frequency of occurrence of each difference and the similarity between the differences, which indicates the degree to which a certain difference and another difference occur in the same instance; If the number or frequency of a first difference, which is a difference that occurred in any of the portions, exceeds a first threshold, and if the similarity between the first difference and a second difference, which is a difference that occurred in a portion different from the first difference, exceeds a second threshold, a revision plan is created that adopts both the first difference and the second difference. How to create a process model.

6. A process model creation method for creating a model that defines a workflow in a process including a plurality of tasks, in order to manage on-site data acquired at the site of each task, comprising: The computer storing said model; creating an instance showing the flow of work that was actually performed based on on-site data acquired at the site, and extracting the difference between the instance and the model as difference data; A method for performing a process to generate a proposed revision of the model based on the difference data, comprising: Accepting specification of multiple conditions, each with a priority, for narrowing down differences to be extracted from an instance or instances from which differences are to be extracted, where differences are extracted when at least one of the conditions is met; Identifying, from the difference data, differences extracted from instances that meet the specified conditions or differences that meet the specified conditions, and if a difference that meets one of the conditions conflicts with a difference that meets another condition, creating a revision proposal for the model by preferentially adopting the difference that meets the condition with the higher priority. How to create a process model.

7. A process model creation method for creating a model that defines a workflow in a process including a plurality of tasks, in order to manage on-site data acquired at the site of each task, comprising: The computer storing said model; creating an instance showing the flow of work that was actually performed based on on-site data acquired at the site, and extracting the difference between the instance and the model as difference data; A method for executing a process that creates a revision proposal for the model based on the differential data, identifies business features to be added to the model in the revision proposal based on differences in data structure between the model and the revision proposal, and displays a structure of the revision proposal on a screen using nodes corresponding to businesses, products, or parts, and arrows connecting the nodes along the flow of the business, extracting, from a plurality of instances, portions that are present in the instances but not in the model, or portions that are present in the model but not in the instances, as differences, and further calculating the number of times or frequency of occurrence of each difference and the similarity between the differences, which indicates the degree to which a certain difference and another difference occur in the same instance; If the number or frequency of a first difference, which is a difference that occurred in any of the portions, exceeds a first threshold, and if the similarity between the first difference and a second difference, which is a difference that occurred in a portion different from the first difference, exceeds a second threshold, a revision proposal incorporating the first difference and the second difference is created, and when a selection operation is performed on a portion corresponding to the first difference in the display of the structure of the revision proposal, the portion corresponding to the second difference is displayed in a distinguishable manner. How to create a process model.

Images