Process model creation system, process model creation method, and process model creation program

Abstract

To propose a process model creation system, a process model creation method, and a process model creation program that can reduce the man-hours required for creating a process model without the need to prepare a process model for each of a plurality of business systems.SOLUTION: A process model creation system includes a data structure conversion unit that converts each data of each business system into a common BOP (Bill of Process) data structure, a model generation unit that creates multiple adapter models from the common BOP data structure, and a process model synthesis unit that extracts the differences between the multiple adapter models and creates a synthesized process model.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a process model creation system, a process model creation method, and a process model creation program, and is suitably applied to a process model creation system that creates a process model to which on-site data from a on-site data generating device installed in production equipment of a factory and design data can be linked, for example. [Background technology]

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

[0003] Patent Document 1 describes a method for collecting and managing on-site data. In Patent Document 1, a process model that models the manufacturing process is generated, and on-site data is managed by linking it to the process model. On the other hand, Patent Document 2 describes a method for generating a process flow model from data. In Patent Document 2, the process flow is modeled by "creating flow information in which the names of updated data sets are arranged in order of update time." [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2019-153051 A [Patent Document 2] International Publication No. WO 07 / 132547 Summary of the Invention [Problem to be solved by the invention]

[0005] According to the disclosed patent documents, it is possible to generate a process model for managing on-site data at a manufacturing site from data managed by a business system at the manufacturing site. However, generally, multiple business systems are in operation at a manufacturing site, and the data structure of the data managed by each business system is different. For this reason, when creating a process model from data managed by a business system, it is necessary to prepare a process model generation function for each of the multiple business systems. For this reason, each time a business is added or changed in each business system, it is necessary to develop individual functions for each business system. Moreover, since the granularity of the definition of the business process differs for each business system, it is difficult to grasp the difference between the process models even when comparing the process models of multiple business systems. This type of problem is not unique to manufacturing sites in the manufacturing industry, but also exists in companies in various other industries. For example, similar problems exist in industries that have a series of processes consisting of multiple tasks and in which multiple business systems are in operation, such as logistics, retail, and service industries.

[0006] The present invention has been made in consideration of the above points, and aims to propose a process model creation system, a process model creation method, and a process model creation program that can reduce the man-hours required for creating a process model without the need to prepare a process model for each of a plurality of business systems. [Means for solving the problem]

[0007] In order to solve such problems, the present invention includes a data structure conversion unit that converts each data for each business system into a common BOP (Bill of Process) data structure, a model generation unit that creates a plurality of adapter models from the common BOP data structure, and a process model synthesis unit that extracts differences between the plurality of adapter models and creates a synthesized process model.

[0008] In the present invention, a data structure conversion step in which a data structure conversion unit of a process model creation system converts each data for each business system into a common BOP (Bill of Process) data structure, a model generation step in which a model generation unit of the process model creation system creates a plurality of adapter models from the common BOP data structure, and a process model synthesis step in which a process model synthesis unit of the process model creation system extracts differences between the plurality of adapter models and creates a synthesized process model.

[0009] In the present invention, a process model creation system has a data structure conversion step in which a data structure conversion unit converts each piece of data for each business system into a common BOP (Bill of Process) data structure, a model generation step in which a model generation unit of the process model creation system creates a plurality of adapter models from the common BOP data structure, and a process model synthesis step in which a process model synthesis unit of the process model creation system extracts differences between the plurality of adapter models and creates a synthesized process model.

[0010] In this way, the process model synthesis unit can generate a synthesized process model based on the differences between a plurality of adapter models. Effect of the Invention

[0011] According to the present invention, it is possible to realize a process model creating system, a process model creating method, and a process model creating program that can reduce the number of steps required to create a process model without the need to prepare a process model for each of a plurality of business systems. [Brief description of the drawings]

[0012] [Figure 1] 1 is a block diagram showing an example of a system configuration of a process model creating system according to an embodiment of the present invention. [Diagram 2]FIG. 2 is a block diagram showing an example of functions of the process model creating system according to the present embodiment. [Diagram 3] FIG. 13 is a diagram illustrating an example of a model generation sequence for generating a composite process model. [Figure 4A] FIG. 2 is a diagram illustrating an example of design data. [Figure 4B] FIG. 11 is a diagram showing an example of on-site data. [Diagram 5] FIG. 1 is a diagram illustrating an example of a relationship between a manufacturing process and a business operation. [Figure 6] FIG. 2 is a diagram illustrating an example of a configuration of a schema model. [Figure 7] FIG. 13 illustrates an example of an achievement instance. [Figure 8] 13 is a flowchart showing an example of a procedure of adapter function processing by an adapter function unit. [Figure 9] 11 is a flowchart illustrating an example of a procedure for a model generation process. [Figure 10] 13 is a flowchart illustrating an example of a procedure for a model synthesis process. [Figure 11] 13 is a flowchart illustrating an example of a procedure for a result instance creation process. [Figure 12] FIG. 2 illustrates an example of a process catalog. [Figure 13] FIG. 13 illustrates an example of a process catalog. [Figure 14] FIG. 13 illustrates an example of a process catalog. [Figure 15] FIG. 13 illustrates an example of a process catalog. [Figure 16] FIG. 13 is a diagram illustrating an example of assistance for creating a process catalog. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0014] 1 is a block diagram showing an example of a system configuration of a process model creation system 100 according to this embodiment. The process model creation system 100 includes business operators A, B, C1, C2, manufacturing sites D1 and D2. Note that the manufacturing site D1 indicates the manufacturing site of business operator C1, and the manufacturing site D2 indicates the manufacturing site of business operator C2.

[0015] The manufacturing site D1 is provided with a plurality of data generating devices 130a, which are provided in the manufacturing equipment of the manufacturing site D1 and collect on-site data of the manufacturing equipment of the manufacturing site D1. The plurality of data generating devices 130a are connected to the network 120.

[0016] A plurality of data generating devices 130b are provided, and a plurality of data generating devices 130a are provided in the manufacturing equipment of the manufacturing site D2 and collect on-site data of the manufacturing equipment of the manufacturing site D2. The plurality of data generating devices 130b are connected to the network 120.

[0017] The business entity A is provided with an operation terminal 180 and a process model creating system 110. The operation terminal 180 is a terminal device operated by a user, and an instruction according to the operation is given to the process model creating system 110, whereby the process model creating system 110 creates a composite process model that can be used in common in a plurality of business systems. That is, in this embodiment, the function of creating a process model is integrated in the process model creating system 110, and each business system does not need to have a function of creating a process model. This is because the process model itself is not essential for the operation of each business system, and rather than each business system needing a function of creating a process model, the information collecting system 170 needs to provide a process model creating function to manage the data of each business system. The process model creating system 110 is a so-called computer equipped with, for example, a central processing unit and a storage unit, and is configured to be able to execute a process model creating program described later using the central processing unit, storage unit, etc.

[0018] The process model may have a task node corresponding to each task, a material node corresponding to the material of each task, and related information nodes related to so-called 4M data items. 4M indicates elements of huMan (worker), Machine (equipment), Method (procedure), and Material (material). The related information may be 1M to 3M information that does not include any one or more of the 4M information. The related information may include information on the quality of the product of the task. The task related information may include information on the environment (Environment) in which the task is performed and information on the management status (Management). Note that the material node may be an input product (part) or an output product (finished product or part) of the task node. In this way, the flow of whether the material node is an input product or an output product for the task node is also expressed as a "process flow". The related information node linked to the task node stores 4M data items related to the task. In this embodiment, a flow consisting of multiple tasks is also expressed as a "process". Here, it is assumed that the identifier for identifying the material in the process does not change.

[0019] The business entity B includes a relationship data model storage unit 150, a relationship data storage unit 160, an information collection system 170, and a network 120, and the relationship data model storage unit 150, the relationship data storage unit 160, and the information collection system 170 are connected to the network 120. Note that the network 120 may be located outside the business entity B.

[0020] The business entity C1 includes a plurality of on-site data storage units 141a and a plurality of design data storage units 142a. The plurality of on-site data storage units 141a and the plurality of design data storage units 142a are connected to the network 120.

[0021] For example, site data generated by a data generating device 130a of the manufacturing site D1 is collected via the network 120 and stored in the multiple site data storage units 141a.

[0022] In the plurality of design data storage units 142a, for example, design data related to products at the manufacturing site D1 is collected and stored via the network 120. Here, the design data includes product configuration information such as part numbers, models, product specifications, product attributes, and quantities.

[0023] The business entity C2 includes a plurality of on-site data storage units 141b and a plurality of design data storage units 142b. The plurality of on-site data storage units 141b and the plurality of design data storage units 142b are connected to the network 120.

[0024] For example, site data generated by a data generating device 130a of the manufacturing site D1 is collected via the network 120 and stored in the multiple site data storage units 141b.

[0025] In the plurality of design data storage units 142b, for example, design data relating to products at the manufacturing site D1 is collected via the network 120 and stored.

[0026] In this embodiment, when there is no need to distinguish between the site data storage unit 141a and the site data storage unit 141b, they will be referred to as the "site data storage unit 141," and when there is no need to distinguish between the design data storage unit 142a and the design data storage unit 142b, they will be referred to as the "design data storage unit 142."

[0027] As described above, in this embodiment, business systems are operated separately for each of the multiple businesses, and the user at business A needs to operate the operation terminal 180 to create a composite process model (hereinafter also referred to as a "schema model") common to the businesses using the process model creation system 110. A specific description will be given below.

[0028] 2 is a block diagram showing an example of the functions of the process model creation system 100 according to this embodiment. As described above, the site data storage unit 141 sequentially stores site data generated by the data generating device 130a and the data generating device 130b, and the design data storage unit 142 stores, for example, design data related to products at the manufacturing site D1 and the manufacturing site D2.

[0029] In this embodiment, the system includes an adapter function unit 210 as an example of a data structure conversion unit that converts each data for each business system into a common BOP (Bill of Process) data structure, a model generation unit 220 that creates multiple adapter models from the common BOP data structure, and a model synthesis unit 250 as an example of a process model synthesis unit that extracts differences between the multiple adapter models and creates a synthesized process model. Here, the above-mentioned data can include, for example, BOP, design data, and site data.

[0030] The above-mentioned process model creating system 110 includes an achievement instance creating unit 260 , an adapter function unit 210 , a model history storing unit 230 , a model generating unit 220 , a catalog storing unit 240 , and a model synthesizing unit 250 .

[0031] The actual result instance creation unit 260 creates actual result instances (see Figure 7 described later) from the site data stored in the site data storage unit 141, and stores in the relationship data storage unit 160 relationship data indicating the relationship between each task in the manufacturing process and the relationship between each task and each site data linked to the task.

[0032] The adapter function unit 210 converts the BOP (Bill of Process) for each business system into a common BOP. Specifically, the adapter function unit 210 converts data (site data, design data) held by each business system into a common BOP data structure. In the following description, the common BOP is also called a "common BOP." In this embodiment, as an example of such conversion, in order to output a certain item, the item to be input and the process for inputting are defined, and a manufacturing process as the transition of the item is defined to create a common BOP. In this embodiment, the common BOP may be created by defining the input business in the process for inputting the item. In this embodiment, the process to be followed by the same item may be defined by defining the ante-post relationship for the process. In this embodiment, the order relationship may be defined between the businesses in a process consisting of multiple businesses. Furthermore, in this embodiment, the process or business may be defined by allocating related resources (=4M) to the process or business.

[0033] The model generation unit 220 creates an adapter model using the common BOP data as input. The model generation unit 220 generates an adapter model that defines the association between each business, each material for each business, and other related information based on input data such as each business, each material for each business, and other related information, and registers the generated adapter model in the model history accumulation unit 230.

[0034] The model history storage unit 230 stores the adapter models created by the model generation unit 220. The adapter models are used to convert the data structure of the process models.

[0035] A process catalog, which is each process definition, is stored in the catalog storage unit 240. The process catalog defines the relationships between components of a plurality of adapter models in order to compare differences between the plurality of adapter models.

[0036] The process catalog defines, for example, for each node in a schema model, a node in an adapter model that matches the node (for example, the bottom of Figs. 12, 13 to 16 described later). One example of a process catalog is a business (node) of a business system of an adapter model that corresponds to a business (node) of a schema model.

[0037] The model synthesis unit 250 has a difference extraction function for extracting differences between adapter models, and creates a synthesized process model based on the differences between the adapter models extracted by the difference extraction function.

[0038] In the present embodiment, the common BOP can be used, for example, to recommend that tasks linked with related information match each other based on the similarity of related information related to tasks in each process model, for example, so-called 4M data items. This recommendation assists in the creation of a process catalog (catalog creation assistance unit). Specific examples of the use form include, for example, tasks being performed at the same location in a factory, using the same equipment, and being handled by the same worker. Another specific example of the use form can be recommended that tasks match each other based on the similarity of the names of each task in each process model. Another specific example of the use form can be changing the accuracy of the recommendation depending on which information is used to estimate the match between tasks based on the hierarchy of BOE (Bill of Equipment) > BOM (Bills of Material) > BOP (Bill of Process).

[0039] The model synthesis unit 250 is an example of a process model synthesis unit, and as described above, generates a synthesized process model as a schema model that can link all of the data in multiple business systems, taking into account the differences extracted by the difference extraction function.

[0040] 3 shows an example of a model generation sequence for generating a composite process model. In this embodiment, the process model creation method is executed by executing a process model creation program in the process model creation system 100. Specifically, the process model creation program causes a computer to execute the following steps in the process model creation system 100: a data structure conversion step in which an adapter function unit 210, which is an example of a data structure conversion unit, converts each data for each business system into a common BOP data structure; a model generation step in which a model generation unit 220 of the process model creation system 100 creates multiple adapter models from the common BOP data structure; and a process model synthesis step in which a model synthesis unit 250 of the process model creation system 100 extracts differences between multiple adapter models and creates a composite process model. The steps are specifically described below.

[0041] First, in step S301, a user operates the operation terminal 180 to issue an instruction to create a schema model to the process model creation system 110. The "schema model" here means a composite process model, and in the following description, this schema model may also be referred to as a composite process model.

[0042] In step S302, the process model creation system 110 executes a data search. Specifically, the process model creation system 110 issues an instruction to the site data accumulation unit 141 to provide site data, and issues an instruction to the design data accumulation unit 142 to provide design data.

[0043] In step S303, when the site data accumulation unit 141 receives an instruction to provide the site data from the process model creating system 110, the site data accumulation unit 141 provides the site data to the process model creating system 110.

[0044] In step S304, when the design data accumulation unit 142 receives an instruction to provide the design data from the process model creating system 110, the design data accumulation unit 142 provides the design data to the process model creating system 110.

[0045] In step S305, the process model creation system 110 creates an adapter model. Here, the adapter model is used to convert the data structure of the process model in order to standardize the data structure of the process model of each business system, instead of each business system creating its own process model as in the past. This eliminates the need for each business system to generate a process model by itself.

[0046] In step S306, the process model creating system 110 creates a schema model. The process model creating system 110 provides the created schema model to the operation terminal 180.

[0047] In step S307, the user operates the operation terminal 180 to edit the schema model as necessary, and provides the edited schema model as a composite process model to the process model creating system 110. In this embodiment, the schema model and the composite process model are described as being substantially synonymous.

[0048] In step S308, the process model creating system 110 provides the edited schema model to the relevance data model storage unit 150. In step S309, the edited schema model is registered in the relevance data model storage unit 150.

[0049] FIG. 4A is a diagram showing an example of design data. In FIG. 4A, three types of design data are illustrated. Design data 410 shown in the upper part of FIG. 4A manages a task identifier 411 and a task name 412 for identifying each task from another. Design data 420 shown in the center of FIG. 4B manages a task sequence identifier 461, a product type identifier 431, and a task sequence 462 of each task. Design data 430 shown in the lower part of FIG. 4A manages a product-part relationship identifier 471, a product type identifier 431, a part type identifier 472, and a task identifier 411. That is, the design data manages, for example, information on the task sequence, product type, task sequence, relationship between products and parts, product type, and part type in the manufacturing process of each task.

[0050] Fig. 4B is a diagram showing an example of site data. Two types of site data are illustrated in Fig. 4B. Site data 440 shown in the upper part of Fig. 4B manages a product identifier 481, a product type identifier 431, a task identifier 411, a work date and time 482, and a part identifier 483. Site data 450 shown in the lower part of Fig. 4B manages a task-related information history identifier 491, a task-related information identifier 421, a product identifier 481, a work date and time 492, and a work result 493.

[0051] 5 is a diagram showing an example of the relationship between a manufacturing process and an operation. A manufacturing process 510 includes a plurality of operations, for example, an operation 520a and an operation 520b. That is, in the manufacturing process 510, it is shown that the operation 520a and the operation 520b may be related to each other.

[0052] 6 is a diagram showing an example of the configuration of a schema model 660. As mentioned above, a schema model may also be called a process model. The schema model 660 represents the relationship between an input node, which is the material for the product of a certain business node, and a finished product, which is the output node of the business, and the relationship between the business node and related information such as on-site data, using edges that connect the two with arrows.

[0053] The schema model 660 includes a business process model definition range 610. In this schema model 660, the business process model definition range 610 is connected by an edge to a business node 622 corresponding to the preceding process as an input, and is connected by an edge to a business node 621 corresponding to the succeeding process as an output.

[0054] The business model definition scope 610 includes one business node 620. In the business model definition scope 610, a material node 630 is connected by an edge as an input product of the business node 620, related information 640 is connected by an edge to the business node 620, and a material node 650 is connected by an edge as an output product of the business node 620.

[0055] 7 is a diagram showing an example of an actual result instance 710. The illustrated example shows an example of the definition range of the actual result instance 710 for, for example, product A. The actual result instance 710 is created by the actual result instance creating unit 260 (see FIG. 2) as described above. Here, as an example, the actual result instance 710 will be described as including two business nodes, 721 and 722.

[0056] A material node 741 as an input product and a material node 742 as an output product are connected to the business node 721 by edges indicated by arrows. For example, the business identifier of the business node 721 is "act_001" and the operation date and time is "2019 / 1 / 1 10:00:00". The component identifier of the material node 741 is, for example, "material_000". The component identifier of the material node 742 is, for example, "material_001".

[0057] The business node 722 is connected to a material node 742 as an input product and a material node 743 as an output product by edges indicated by arrows. For example, the business node 722 has a business identifier of "act_002" and an operation date and time of "2019 / 1 / 1 10:00:00". The component identifier of the material node 742 is "material_001". The component identifier of the material node 743 is "material_001".

[0058] 8 is a flowchart showing an example of a procedure of adapter function processing. The adapter function processing is processing executed by the adapter function unit 210. In step S811, the adapter function unit 210 acquires at least one of the site data and the design data in response to an instruction from the operation terminal 180. In step S802, the adapter function unit 210 converts the data structure of each data based on the acquired site data and design data.

[0059] 9 is a flowchart showing an example of the procedure of the model generation process. This model generation process is a process executed by the model generation unit 220. In step S821, the model generation unit 220 generates an adapter model (to be described later) based on the above-mentioned input data. In step S822, the model generation unit 220 registers the generated adapter model in the model history accumulation unit 230.

[0060] 10 is a flowchart showing an example of the procedure of the model synthesis process. This model synthesis process is executed by the model synthesis unit 250. In step S831, the model synthesis unit 250 acquires a process catalog registered in the catalog storage unit 240. In step S832, the model synthesis unit 250 acquires an adapter model registered in the model history storage unit 230.

[0061] In step S833, the model synthesis unit 250 uses this adapter model to convert the data structure of the process model of each business system to create a schema model.

[0062] In step S834, the model synthesis unit 250 repeatedly executes steps S835 and S836 until the user finishes editing. In step S835, the model synthesis unit 250 edits the schema model. In step S836, the model synthesis unit 250 updates the process catalog (see FIG. 9, the lower part of FIG. 13 and the lower part of FIG. 14 described later) registered in the catalog storage unit 240 (see the lower part of FIG. 15 described later).

[0063] In step S837, the model synthesis unit 250 registers the schema model in the relationship data model storage unit 150.

[0064] 11 is a flowchart showing an example of the procedure of the result instance creation process. This result instance creation process is executed by the result instance creation unit 260. In step S841, the result instance creation unit 260 acquires site data registered in the site data accumulation unit 141. In step S842, the result instance creation unit 260 creates a result instance.

[0065] In this embodiment, the adapter function unit 210 is an example of a data structure conversion unit, and converts each piece of data that differs for each business system to fit the data structure of a common BOP so that the data structure of each piece of data for each business system is common.

[0066] In this embodiment, the adapter function unit 210 converts data (site data, design data) that differs for each business system to fit the data structure of the common BOP. Note that the user may be allowed to edit the process flow hierarchy defined in the business system and the process-business hierarchy mapping in the common BOP.

[0067] In this embodiment, the adapter function unit 210 is an example of a data structure conversion unit, and redefines a common BOP that is common to the BOPs that link each data.

[0068] The model synthesis unit 250 is an example of a process model synthesis unit, which adjusts each process definition in each business system based on the above-mentioned differences, and generates a schema model as a synthesized process model from each adjusted process definition (process catalog).

[0069] In this embodiment, the process model creating system 110 generates a composite process model by estimating a schema model based on an example of a process catalog as shown below, from the differences between a plurality of adapter models.

[0070] 12 is a diagram showing an example of a process catalog. The illustrated process catalog shows, for a node in a schema model, a node in an adapter model that matches the node. For example, it shows that it is estimated that the node of business a in the schema model corresponds to the node of business (1) in business system I or the node of business A in business system II. It shows that it is estimated that the node of business b in the schema model corresponds to the node of business (2) in business system I, or business B1-L1, business B2-L1, business B1-L2, and business B2-L2 in business system II.

[0071] 13 is a diagram showing an example of creating a process catalog. The illustrated example shows an example at the time of initial construction. An adapter model P910 at the time of initial construction has a node P920a of a business A, a node P920b of a business B, a node P920c of a business C, a node P920d of a business D, and a node P920e of a business D.

[0072] In the initially constructed adapter model P910, in addition to the material node P930m, the node P940p of related information P is connected as an input to the node P920a of business A, and the material node P930a is connected as an output.

[0073] The material node P930a is connected to the node P920b of the business B as an input product of the node P920b of the business B, and the node P920b of the business B is connected to the material node P930b as an output product of the node P920b of the business B. The material node P930b is an input product of the node P920c of the business C, and the node P920c of the business C is connected to the material node P930c as an output product of the node P920c of the business C.

[0074] The material node P930c is connected to the node P920d of task D as an input product of the node P920d of task D, and the node P920d of task D is connected to the material node P930d as its output product. The node P920d of task D is connected to the related information P940q. This material node P930d is an input product of the node P920e of task E, and the node P920e of task E is connected to the material node P930e as its output product.

[0075] The adapter model P910 at the time of initial construction coincides with the schema model S910 in form (except for the symbol).

[0076] The process catalog 900 manages nodes in the adapter model that match the nodes in the schema model. The model synthesis unit 250 makes the following estimations. It is estimated that the node S920a of the business A of the system (adapter model) P corresponds to the node P920a of the business A of the schema model. It is estimated that the node S920b of the business B of the system (adapter model) P corresponds to the node P920b of the business B of the schema model. It is estimated that the node S920c of the business C of the system (adapter model) P corresponds to the node P920b of the business B of the system (adapter model) P corresponds to the node C of the schema model. It is estimated that the node S920d of the business D of the system (adapter model) P corresponds to the node D of the schema model. It is estimated that the node S920e of the business E of the schema model corresponds to the node S920e of the business E of the system (adapter model) P corresponds to the node S920e of the business E of the system (adapter model) P.

[0077] Fig. 14 is a diagram showing an example of creating a process catalog. The illustrated example shows an example at the time of initial construction. An adapter model Q910 at the time of initial construction has a node Q920a of a business A, a node Q920b of a business B, and a node Q920d of a business D. That is, the process catalog shown in Fig. 14 differs from the process catalog in Fig. 13 in terms of its form (except for the reference numerals) in that the node P920c of a business C is omitted.

[0078] In the initially constructed adapter model Q910, in addition to the material node Q930m, the related information P node Q940p is connected as an input to the business A node Q920a, and the material node Q930a is connected as an output.

[0079] Material node Q930a is connected to node Q920b of business B as an input product to node Q920b of business B, which is connected to material node Q930b as an output product. This material node Q930b is an input product to node Q920d of business D, which is connected to material node P930d as an output product. Related information P940q is connected to the node of business D.

[0080] The adapter model P910 at the time of initial construction does not match the node schema model S910 of the business E in terms of the form of the process catalog, and a node S920e of the business E and a material node S930e as its output product have been added.

[0081] As described above, the process catalog 900 manages nodes in the adapter model that match nodes in the schema model. The model synthesis unit 250 makes the following estimations. It is estimated that node Q920a of the business A in the system (adapter model) P corresponds to node S920a of the business A in the schema model. It is estimated that node Q920b of the business B in the system (adapter model) P corresponds to node S920b of the business B in the schema model.

[0082] It is presumed that node S920d of business D in the schema model corresponds to node P920d of business D in system (adapter model) P. It is presumed that node S920e of business E in the schema model should originally correspond to node Q920e of business E, if node Q920e of business E in system (adapter model) P exists.

[0083] Fig. 15 is a diagram showing an example of creating a process catalog. The illustrated example shows an example at the time of update. The adapter model Q910 at the time of update has a node Q920a of a business A, a node Q921b of a business B1, a node Q922b of a business B2, a node Q920c of a business C, a node Q920d of a business D, and a node Q920e of a business E. That is, the process catalog shown in Fig. 15 is different from the process catalog in Fig. 13 in that a node Q921b of a business B1 and a node Q922b of a business B2 are provided instead of the node P920b of a business B. The following mainly describes the differences from the example shown in Fig. 13.

[0084] In the updated adapter model Q910, material node Q930a is connected as an output product of node Q920a of business A as an input product of node Q921b of business B1, and material node P931b is connected as an output product of node Q921b of business B1. This material node P931b is connected as an input product of business B2 as an input product of business B2, and material node P932b is connected as an output product of business B2.

[0085] On the other hand, the schema model S910a at the time of update differs in form from the schema model S910 at the time of initial construction shown in Fig. 13 mainly in that the node S920c of business C is omitted. Therefore, it can be said that the schema model S910a at the time of update has a different granularity in the definition of the manufacturing process compared to the adapter model Q910 at the time of update.

[0086] As described above, the process catalog 1000 manages nodes in the adapter model that match nodes in the schema model. The model synthesis unit 250 makes the following estimation. It is estimated that the node S920a of the business A in the schema model corresponds to the node S920a of the business A in the system (adapter model) P. It is estimated that the node P920b of the business B in the schema model corresponds to the node S921b of the business B1, the node S922b of the business B2, and the node P920c of the business C in the system (adapter model) P.

[0087] It is presumed that node P920d of business D in the schema model corresponds to node P920d of business D in system (adapter model) P. It is presumed that node P920e of business E in the schema model corresponds to node P920e of business E in system (adapter model) P.

[0088] 16 is a diagram showing an example of assistance in creating a process catalogue. An adapter model R1110 has a node R1120a for a task A1, a node R1120b for a task A2, a node R1120c for a task B1, a node R1120d for a task B2, and a node R1120e for a task C1.

[0089] In the adapter model R1110, in addition to the material node R1130m, a node R1140p of related information P is connected as an input product to a node R1120a of the task A1, and a material node R1130a is connected as an output product.

[0090] Material node R1130a is connected to node R1120b of task A2 as an input product of node R1120b of task A2, and node R1120b of task A2 is connected to material node R1130b as its output product. This material node R1130b is an input product of node R1120c of task B1. Node R1120c of task B1 is connected to material node R1130c as its output product. This material node R1130c is an input product of node R1120d of task B2. Node R1120d of task B2 is connected to node R1140q of related information Q. Node R1120d of task B2 is connected to material node R1130d as its output product.

[0091] The material node R1130d is connected to the node R1120e of the task C1 as an input product of the node R1120e of the task C1, and the node R1120e of the task C1 is connected to the material node R1130e as an output product thereof.

[0092] This adapter model R1110 does not match the schema model S1110 in its form (except for the symbol).

[0093] The process catalog 1100 manages nodes in the adapter model that correspond to nodes in the schema model. For node S1120a of business A in the schema model, it is estimated that node R1120a of business A1 and node R1120b of business A2 in the system (adapter model) R correspond to the node S1120a of business A in the schema model, as shown by the dashed line.

[0094] It is estimated that node S1120b of service B in the schema model corresponds to node R1120c of service B1 and node Q1120d of service B2 in system (adapter model) R, based on the estimation shown by the dashed dotted line.

[0095] It is presumed that node R1120e of the service C1 of system (adapter model) R corresponds to node S1120b of the service C in the schema model, based on the presumption shown by the dashed dotted line.

[0096] In this way, the model synthesis unit 250 estimates the correspondence between the business operations of the adapter model and the schema model, thereby adjusting the differences between the schema models (process models) of each business system, and can create a common synthesized process model for each business system.

[0097] As described above, the process model creation system 100 according to this embodiment includes an adapter function unit 210 as an example of a data structure conversion unit that converts each data for each business system into a common BOP (Bill of Process) data structure, a model generation unit 220 that creates a plurality of adapter models from the common BOP data structure, and a model synthesis unit 250 as an example of a process model synthesis unit that extracts differences between the plurality of adapter models and creates a synthesized process model.

[0098] Furthermore, in this embodiment, an adapter function unit 210 as an example of a data structure conversion unit of the process model creation system executes a data structure conversion step in which each data for each business system is converted into a common BOP (Bill of Process) data structure, a model generation step in which a model generation unit 220 of the process model creation system 100 creates a plurality of adapter models from the common BOP data structure, and a process model synthesis step in which a process model synthesis unit 250 of the process model creation system 100 extracts differences between the plurality of adapter models and creates a synthesized process model.

[0099] In this way, it is not necessary to generate a process model for each of a plurality of business systems, and it is sufficient to generate only a composite process model, thereby reducing the man-hours required to generate a process model corresponding to each business process.

[0100] In this embodiment, the adapter function unit 210 converts each piece of data that differs for each business system to fit the data structure of the common BOP so that the data structure of each piece of data for each business system is common. In this way, there is no need to generate a process model for each of multiple business systems, and it is sufficient to simply generate a composite process model from the adapter model of the adapter function unit 210, which reduces the man-hours required to generate a process model in accordance with each business process.

[0101] In this embodiment, the adapter function unit 210 is an example of a data structure conversion unit, and redefines a common BOP that is common to the BOPs that link each data. In this way, it is not necessary to generate a process model for each of a plurality of business systems, and it is sufficient to generate a composite process model from the common BOP, so that the man-hours required to generate a process model corresponding to each business process can be reduced.

[0102] The model synthesis unit 250 is an example of a process model synthesis unit, which adjusts each process definition in each business system based on the difference between multiple adapter models, and generates a schema model as a synthesized process model from each adjusted process definition. In this way, it is not necessary to generate a process model for each of multiple business systems, and it is sufficient to simply generate a synthesized process model from each process definition, so that the man-hours required to generate a process model corresponding to each business process can be reduced.

[0103] In addition, in this embodiment, as a common usage mode of BOP, it recommends matching of tasks linked with related information related to the tasks, and assists in the creation of a process catalog. In this way, a process model can be easily created.

[0104] (3) Other modifications In this embodiment, the process model creation system 110 is provided at business operator A, but the present invention is not limited to this, and the process model creation system 110 may be provided at another business operator, for example, business operator B, business operator C1, or business operator C2. [Industrial Applicability]

[0105] The present invention can be applied to a process model creation system that creates a process model to which on-site data from a on-site data generating device installed in production equipment of a factory and design data can be linked.

[0106] In the above embodiment, an example of a manufacturing process at a manufacturing site has been described, but the process model creation system 110 can be applied to any business type that is composed of multiple tasks and operates multiple business systems, not limited to manufacturing sites. For example, in the logistics or transportation industry, there are multiple steps that make up the transportation process from receiving luggage to sorting, storage, packaging, and delivery, and a transportation process model can be created from on-site data and planning data related to the transportation process in the same way as a process model at a manufacturing site. [Explanation of symbols]

[0107] 110: process model creation system, 120: network, 130a, 130b: data generation devices, 141a, 141b: site data storage units, 142a, 142b: design data storage units, 150: relationship data model storage units, 160: relationship data storage units, 180: operation terminals.

Claims

1. A data structure conversion unit that converts each data of each business system into a common BOP (Bill of Process) data structure; a model generation unit for generating a plurality of adapter models from the data structure of the common BOP; a process model synthesis unit that extracts differences between the plurality of adapter models and creates a synthesized process model; A process model creation system comprising:

2. The data structure conversion unit is In order to make the data structure of each data in each business system common, each data that differs for each business system is converted to fit the data structure of the common BOP.

2. The process model creating system according to claim 1.

3. The data structure conversion unit is Based on the difference, a common BOP common to the BOPs that link the different data for each business system is redefined.

2. The process model creating system according to claim 1.

4. The process model synthesis unit Based on the difference, each process definition in each of the business systems is adjusted, and the composite process model is generated from each of the adjusted process definitions.

2. The process model creating system according to claim 1.

5. Each data for each of the multiple business systems at the manufacturing site is either BOP, site data, or design data.

2. The process model creating system according to claim 1.

6. As a usage mode of the common BOP, a catalog creation assistance unit is provided that recommends matching of tasks that are linked with related information related to the tasks and assists in creating a process catalog.

2. The process model creating system according to claim 1.

7. a data structure conversion step in which a data structure conversion unit of the process model creation system converts each data of each business system into a common data structure of BOP (Bill of Process); a model generation step in which a model generation unit of the process model creation system generates a plurality of adapter models from the data structure of the common BOP; a process model synthesis step in which a process model synthesis unit of the process model creation system extracts differences between the plurality of adapter models and creates a synthesized process model; 1. A process model creating method in a process model creating system, comprising:

8. In the data structure conversion step, A data structure conversion unit converts each piece of data that differs for each of the business systems into a data structure that matches the common BOP so that the data structure of each piece of data for each of the business systems is common.

8. The process model creating method according to claim 7.

9. The data structure conversion step includes: A redefinition unit redefines a common BOP that is common to the BOPs that link each of the data.

8. The process model creating method according to claim 7.

10. The process model synthesis unit Based on the difference, each process definition in each of the business systems is adjusted, and the composite process model is generated from each of the adjusted process definitions.

8. The process model creating method according to claim 7.

11. Each data for each of the multiple business systems at the manufacturing site is either BOP, site data, or design data.

8. The process model creating method according to claim 7.

12. The catalog creation support unit has a catalog creation support step of recommending that tasks linked with related information related to the tasks coincide as a usage mode of the common BOP, and supporting the creation of a process catalog.

8. The process model creating method according to claim 7.

13. a data structure conversion step in which a data structure conversion unit converts each data of each business system into a common data structure of a BOP (Bill of Process) in the process model creation system; a model generation step of causing a model generation unit of the process model creation system to create a plurality of adapter models from the data structure of the common BOP; a process model synthesis step of causing a process model synthesis unit of the process model creation system to extract differences between the plurality of adapter models and create a synthesized process model; A process model creation program that causes a computer to execute the above steps.

Images