JP5007609B2 - Production order creation program and production order creation device - Google Patents

Description

  The present invention relates to a production order creation program and a production order creation apparatus.

A manufacturing execution system (MES) is used in order to cope with the production of a wide variety of small lots.
Patent Document 1 includes a step in which a manufacturing instruction program that generates manufacturing instruction data for manufacturing a product based on a manufacturing plan calculates a possible number of starts that can manufacture a product from supply procurement data that reflects the procurement results of parts; , Calculating a surplus number for each part from the possible start number, releasing both surplus numbers for each part in the supply procurement data, and creating manufacturing instruction data based on the possible start number Are listed. Thereby, a manufacturing instruction can be issued so as not to generate surplus parts.

  Patent Document 2 discloses a workflow management system that defines a manufacturing process of a product by a plurality of work items and a work order in an apparatus for managing a workflow of a manufacturing process or a paperwork process, and manages execution work based on the definition. , The execution mode indicating the work state of the work item and the execution instruction mode indicating the work item ready-to-start state are monitored, and the abnormal state of the work item is continuously detected from the execution mode and the execution instruction mode for a certain period. It is described that the corresponding work item is notified as a problem occurrence state.

By the way, in a manufacturing execution system, when a manufacturing instruction is made based on production plan data, a manufacturing instruction, a manufacturing process, a manufacturing method, and the like are different for each user. Therefore, it is necessary to customize a program for performing a manufacturing instruction for each user. There is a problem that it takes time to correct the program from the viewpoint of developing the manufacturing execution system. Further, even when viewed from the user side, there is a problem that the program needs to be corrected when the manufacturing process and the manufacturing method are changed.
JP 2005-316588 A JP-A-9-259181

  An object of the present invention is to enable production instructions to be created with a common program for production systems of different production processes and production methods.

The manufacturing order creation program of the present invention is a program for performing a manufacturing order in a manufacturing execution system that executes production of a part or product, and is an instruction that associates a planning group ID for specifying production plan data for a part or product with an instruction group ID. A step of receiving a definition of an expansion definition master; a step of receiving a definition of an instruction expansion execution application master for associating the instruction group ID with an application executed in the instruction expansion; and an instruction table master for associating the instruction group ID with an instruction table A step of receiving a definition of a plurality of columns of the instruction table, a step of receiving a definition of an instruction expansion detailed definition master that associates data stored in each column, and a reference to the plan group ID with reference to the instruction expansion definition master. Obtaining an instruction group ID to be executed; sequentially executing an application registered in association with the obtained instruction group ID in the instruction development execution application master; data obtained from the production plan data; and the application Is stored in the corresponding column of the instruction table defined in the instruction expansion detailed definition master and the instruction is expanded by the computer.

According to this invention, even when a manufacturing process, a manufacturing method, and the like differ depending on a user, a manufacturing instruction can be performed using a common program.
In the manufacturing order creation program of the above invention, a step of receiving a definition of a plan capture execution application master for associating the plan group ID with an application executed in plan capture, and a plan table definition for associating the plan group ID with a plan table Receiving a definition of a master; receiving a definition of a plan capture detailed definition master that associates a column name of the plan table with a data item name of the production plan data; and A step of sequentially executing the applications registered in association with the group ID; and the production plan data and the execution result data of the application are stored in the plan table defined in the plan capture detailed definition master And performing a planned acquisition and store the item to.

  By configuring in this way, a common plan capturing program can be provided to a plurality of users, so that it is not necessary to customize the program in order to match the difference in the user's manufacturing process.

  In the manufacturing order creation program of the above invention, a step of receiving a definition of an instruction output execution application master for associating the instruction group ID with an application executed in the instruction output, and an instruction output definition for associating the instruction group ID with a data set ID A step of receiving a master definition, a step of receiving a definition of an instruction output detailed definition master that associates a data item name of the instruction data with a column name of the instruction table, and the instruction output execution application master corresponding to the instruction group ID The step of executing the registered application, the data of each column of the instruction table, and the data of the execution result of the application are the instruction data defined in the instruction output detailed definition master Comprising storing the corresponding data item.

  With this configuration, a program for outputting an instruction can be made common to a plurality of users, so that it is not necessary to customize the program in accordance with a difference in the manufacturing process of the users.

In the manufacturing order creation program of the above invention, the instruction expansion detailed definition master includes, as its data structure, at least data of each column of the order table, application execution result data, production plan data data, and It has storage data classification data indicating which data of data automatically set by the manufacturing execution system is stored.

  By configuring in this way, it is possible to store production plan data data, application execution result data in the corresponding item of the instruction table, based on the storage data classification data of the instruction expansion detailed definition master, the system The system can determine whether to store the data created by.

  According to the present invention, even when a manufacturing process, a manufacturing method, and the like differ depending on a user, a manufacturing instruction can be performed using a common program.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing a configuration of a manufacturing execution system (MES) according to the first embodiment of this invention.
The manufacturing execution system according to the embodiment conforms to ISO-S88, and assumes four hierarchical performance models of procedure, unit, operation, and phase. This embodiment can also be applied to systems other than ISO-S88.

  The manufacturing execution system according to the first embodiment has a function of creating manufacturing instruction data for instructing the manufacture of a product or a part based on manufacturing plan data given from a higher system and outputting it to a lower system.

In FIG. 1, a production order creation unit (production order creation device) 11 of the production execution system includes a plan capture unit 12, an instruction development unit 13, and an instruction output unit 14.
When the host system stores production plan data (hereinafter referred to as plan data) in a predetermined folder, the plan capture unit 12 refers to a predefined plan capture system master table 15, An execution application (for example, plan capture processing (standard provision I / F )) associated with the plan group ID is executed. Then, the execution result data is stored in the plan database 16 .

  The instruction expanding unit 13 sequentially executes an execution application (for example, an instruction expanding process) associated with the plan group ID with reference to the instruction expanding system master 17 defined in advance by the user. Then, the execution result data is stored in the instruction table of the instruction database 18.

  In the first embodiment, a general-purpose program (standard provision I / F) is prepared as a program used in the manufacturing instruction creating unit 11, and a manufacturing process, a manufacturing process, a manufacturing method, etc. are prepared for each user. Even if they are different, a general-purpose program can be used by defining a correspondence relationship in the instruction development system master 17.

The instruction output unit 14 refers to the instruction output system master 19 defined in advance by the user, sequentially executes an execution application (for example, an instruction output process) associated with the instruction group ID, and process result data Is output as instruction data.

  The processing result data of the instruction output unit 14 is converted into a specific data format according to the definitions of the transmission definition master 74 and the transmission data definition master 75 (FIG. 3) by the transmission function and the data conversion function, and is output to another system. .

  The manufacturing execution system according to the first embodiment provides an engineering tool that allows a user to individually define a plan capture system master 15, an instruction development system master 17, and an instruction output system master 19. By providing such an engineering tool, production order data can be automatically generated using general-purpose programs (plan capture processing, order expansion processing, etc.) from planning data for different manufacturing processes, manufacturing methods, and product items. Can be generated automatically.

  First, a definition method for defining the plan capture system master 15, the instruction development system master 17 and the instruction output system master 19 using an engineering tool will be described with reference to FIGS.

FIG. 2 is an explanatory diagram of the plan definition. The plan capture definition screen 31 shown in FIG. 2 is displayed by the engineering tool for plan definition. On the plan capture definition screen 31, the user can select any plan table for any plan group. Since a list of all plan tables is displayed on the plan capture definition screen 31, a specific plan table is selected from the list. The selected plan table is registered in the group definition master 55 (see FIG. 3) in association with the plan group ID (data for specifying plan data) (FIGS. 2 and 1).

  Details of the selected plan table are separately defined on the table definition and layout definition screen. The planned group can be registered on the series / group registration screen.

  Next, transmission data to be input source of data in the plan table is selected from the entire transmission data list. The selection result is registered in the plan capture definition master 56 (FIG. 3) in association with the plan group ID (FIGS. 2 and 2).

  Next, the user AP selection screen 32 for plan capture is displayed, and the user AP to be executed at the time of plan capture is selected from the displayed user APs (applications). The selected user AP is registered in the engine execution AP master 54 (FIG. 3) in association with the plan group ID (FIGS. 2 and 3).

The user AP selection screen 32 of FIG. 2 shows a state in which the plan capture process (standard provision I / F) is selected as an execution AP from among a plurality of user APs.
Next, the storage data selection screen 33 is displayed, and the correspondence between the columns of the plan table and the data items of the transmission data is defined. The column name and data item name selected on the stored data selection screen 33 are registered in the plan capture detailed definition master 57 (FIG. 3) in association with the plan table name (FIGS. 2 and 4).

FIG. 3 is a diagram illustrating an example of the plan capture transmission master 20 and the plan capture master 15.
The plan acquisition transmission system master 20 includes a transmission definition master table 51 and a transmission data definition master table 52.

In the transmission definition master 51, data indicating a transmission destination system ID, a transmission destination system, a transmission division, a transmission / reception division, a data division (for example, a plan), and a folder name are registered.
In the transmission data definition master table 52, transmission destination system ID, data set ID, data set name (for example, plan 1), file name, and data indicating the data format are registered.

  The plan capture system master 15 includes a plan group transmission related definition master table 53, an engine execution AP master table 54 (corresponding to a plan capture execution application master), and a group table definition master table 55 (plan table) shown in FIG. Corresponding to a master), a plan capture definition master table 56, and a plan capture detail definition master table 57.

In the planning group transmission related definition master table 53, a transmission system ID and a planning group ID are registered.
The engine execution AP master table 54 includes a function category (for example, plan), a request type (for example, capture), a plan group ID, an instruction group ID, an instruction ID, an execution order, and an execution application (for example, , Data indicating the planned capture processing) is registered.

In the group table definition master table 55, the plan group ID and the table name of the plan table are registered.
In the plan capture definition master table 56, a transmission destination system ID, a data set ID, and a plan group ID are registered.

In the plan capture detailed definition master table 57, data indicating the plan table name, column name, storage data classification (transmission, automatic), data item name, and the like are registered. The plan capture detailed definition master 57 defines the correspondence between the data stored in each column of the plan table and the data of each column of the received plan data.

  FIG. 4 is an explanatory diagram of the instruction development definition. The instruction development definition screen 34 shown in FIG. 4 is displayed by the engineering tool for instruction development definition. On the order development definition screen 34, the user can associate the order group with the order table. Since a list of all instruction tables is displayed on the instruction expansion definition screen 34, the user can select a specific instruction table from the list. The selected instruction table is registered in the group table definition master 62 (FIG. 5) in association with the instruction group ID selected at that time (FIGS. 4 and 5). The details of the instruction table to be selected are separately defined on the table definition screen and layout definition screen.

  In addition to this, it is possible to display a list of all plan tables, a list of all master tables, and a list of all view data, and select a plan table, a master table, and a view from which an instruction table is input (FIG. 4, ( 6)). Details of the plan table, master table, and view to be selected are separately defined on the table definition screen and layout definition screen.

  Next, the user AP selection screen 35 for order development is displayed, and the user AP executed at the time of order development is selected. The selected user AP is registered in the engine execution AP master 61 (FIG. 5) in association with the instruction group ID (FIGS. 4 and 7).

  The user AP selection screen 35 in FIG. 4 includes four user APs, which are lot number issue numbers (standard provided I / F), instruction development logic, measurement count update, and manufacturing workflow notification (standard provided I / F) as execution APs. The selected state is shown. The user AP information can be separately registered on the user AP registration screen.

  Next, the storage data selection screen 36 of FIG. 4 is displayed, and the data to be stored in each column of the instruction table is defined. This result is registered in the instruction development detailed definition master 64 (FIG. 5) in association with the instruction table name (FIGS. 4 and 8).

FIG. 5 is a diagram illustrating an example of the instruction development system master 17. The instruction expansion system master 17 includes an engine execution AP master 61 (corresponding to the instruction expansion execution application master), a group table definition master table 62 (corresponding to the instruction table master), an instruction expansion definition master table 63, and an instruction expansion. It consists of a detailed definition master table 64, a correlation definition master table 65, a parts master table 66, and a manufacturing method master table 67.

The engine execution AP master 61 has the same data configuration as the engine execution AP master 54 of FIG. In the example of FIG. 5, “instruction” is registered as the function category, and “deployment” is registered as the request type.

  In the group table definition master 62, data indicating a group ID and a table name is registered. In the example of FIG. 5, “instruction table 1” and “instruction table 2” are registered in association with the instruction group ID “SG1”.

  In the instruction development definition master 63, data indicating an instruction table name, an instruction ID, and an instruction group ID are registered. In the example of FIG. 5, “instruction table 1” and “instruction table 2” are registered as instruction table names.

The instruction development detailed definition master 64 registers data indicating an instruction table name, a column name, a storage data category (for example, user AP, automatic, plan, master), a table name, and an execution AP ID . The instruction development detailed definition master 64 can define data to be stored in each column of the instruction table.

  In the correlation definition master 65, data indicating a reference source table name, a reference source column name, a target table name, and a target column name are registered. With this correlation definition master 65, it is possible to define the table name and column name of the reference destination of the data of the column for which “master” is set as the storage data category of the instruction development detailed definition master 64.

  In the parts master 66, data indicating items and parts defined in the correlation definition master 65 is registered. Similarly, in the manufacturing method master 67, data indicating items, manufacturing methods, and management items defined in the correlation definition master 65 is registered.

  Next, FIG. 6 is an explanatory diagram of the instruction output definition. The instruction output definition screen 37 in FIG. 6 is displayed by the engineering tool for instruction output definition. In this instruction output definition screen 37, when the user designates an output destination transmission destination system and selects an instruction group and an instruction table, the selection result is associated with the transmission destination system ID, and the instruction output definition master 72 in FIG. (FIG. 6, (9)).

  Next, the storage data selection screen 38 is displayed and data to be output is defined. This definition result is registered in the instruction output detailed definition master table 73 in FIG. 7 in association with the transmission destination system ID and the instruction table name (FIG. 6, (10)). The instruction output detailed definition master 73 can define the correspondence between the data item name of the instruction data that is output data, the column name of the instruction table, and the transmission destination system.

  FIG. 7 is a diagram illustrating an example of an instruction output system master 19 and an instruction output transmission system master 20. The instruction output system master 19 includes an engine execution AP master table 71, an instruction output definition master table 72, and an instruction output detailed definition master table 73. The transmission master 20 for outputting instructions includes a transmission definition master table 74 and a transmission data definition master 75.

  The engine execution AP master 71 (corresponding to the instruction output execution application master) is a table that associates the instruction group and the instruction ID with the execution application, and the data structure thereof is the engine execution AP masters 54 and 61 of FIGS. The same. In the engine execution AP master 71, an application to be executed for a specific instruction ID in the instruction output process is registered.

  In the instruction output definition master 72, data indicating an instruction group ID, an instruction ID, a transmission destination system ID, and a data set ID are registered. The instruction output definition master 72 can define the output destination of the instruction data.

In the instruction output detailed definition master 73, data indicating a transmission destination system ID, a data set ID, a data item name, an instruction table name, and a column name is registered.
The transmission definition master 74 and the transmission data definition master 75 have the same data configuration as the transmission definition master 51 and the transmission data definition master 52 of FIG.

FIG. 8 is a diagram showing a sequence / group registration screen displayed by the engineering tool.
As shown in FIG. 8, since a plurality of instruction group names and instruction registration screens are displayed for one plan group, any plan group can be selected by selecting any order group and order name among them. Any instruction group and instruction ID can be registered.

  The plan capture process, the instruction expansion process, and the instruction output process of the instruction generation unit 11 after the definition of the plan capture, the instruction expansion, and the instruction output are performed as described above will be described. Hereinafter, description will be made on the assumption that the plan capture system master 15 shown in FIG. 3, the instruction development system master 17 shown in FIG. 5, and the instruction output system master 19 shown in FIG. 7 are defined in advance by the user.

  First, the plan capture process of the plan capture unit 12 will be described. When the plan data is input from the host system to the designated folder, the plan capturing unit 12 acquires the plan data from the designated folder (step S11).

Next, a plan group ID corresponding to the transmission destination system ID is acquired with reference to the plan group transmission related definition master 53 of FIG. 3, and a plan capture request queue is issued (step S12).
When, for example, the plan data 81 as shown in FIG. 9 is received by the processing of step S12 described above, the plan capture unit 12 refers to the plan group transmission related definition master 53 and sets the transmission destination system ID “RecvPlan01”. A corresponding plan group ID “P1” is acquired, and a plan capture request queue comprising data of function classification “plan”, request type “capture”, plan group ID “P1”, and file name “D: RecvPlan01.csv” Issue 82.

Next, referring to the plan capture request queue 82 and the engine execution AP master 54, the execution APs defined in association with the plan group ID are executed in order (step S13).
In the example of FIG. 3, since the “plan capture process” is registered as the execution AP in association with the plan group ID “P1” in the engine execution AP master 54, the “plan capture process” is executed. Is done.

  Next, referring to the group table master 55, the plan capture definition master 56, and the plan capture detail definition master 57, the data of each item of the plan data 81 is stored in the designated plan table (step S14).

  By the above step S14, the data of the corresponding data item of the plan data 81 is stored and stored in the column of the plan table in which the storage data classification of the plan capture detailed definition master 57 in FIG. Data is automatically stored in the column whose data classification is “automatic” by the plan capturing unit 12.

  In the plan capture detailed definition master 57 in FIG. 3, “transmission” is defined as the storage data category of the column name “plan management No”, so the data of the plan data 81 in FIG. 9 transmitted from the higher system. The data “P0001” of the item name “plan management No” is stored in the column of the column name “plan management No” in the plan table 1 of FIG.

  Further, since “automatic” is set as the storage data classification of the column name “plan group ID” in the plan capture detailed definition master 57, the plan capture unit 12 uses the column name “plan” in the plan table 83 of FIG. In the “Group ID” column, the plan group ID “P1” registered in the group table definition master 55 of FIG. 3 is set.

  As described above, the user defines data in the plan group transmission related definition master 53, the engine execution AP master 54, the plan capture definition master 56, and the plan capture detail definition master 57 in advance, and the plan capture program By executing the processing with reference to the master, it is possible to process the planning data such as manufacturing processes, manufacturing methods, product items, etc., which are different for each user, with a common plan capturing program.

Next, the instruction development process executed by the instruction development unit 13 will be described with reference to FIGS.
When a specific plan group is selected and the instruction expansion button is operated while the instruction expansion screen is displayed, the instruction expansion unit 13 issues an instruction expansion request queue for the selected plan group (step S21). .

The instruction development request queue 91 shown in FIG. 10 stores data of function classification, request type, plan group ID, and plan management number.
Next, referring to the information in the instruction development request queue 91 and the engine execution AP master 61 in FIG. 5, the execution APs registered in the engine execution AP master 61 are executed in order (step S22).

  In the engine execution AP master 61 of FIG. 5, “instruction development process” and “workflow notification process” are registered as execution APs in association with the plan group ID “P1” and the instruction group ID “SG1”. These processes are executed in order. In the example of FIG. 5, since the execution order of the “instruction development process” is “1” and the execution order of the “workflow notification process” is “2”, the “instruction development process” is executed first.

  Next, data is stored in the instruction table with reference to the group table definition master 62, the instruction expansion definition master 63, the instruction expansion detailed definition master 64, and the plan table 83 of FIG. 9 (step S23).

  In the group table definition master 62 of FIG. 5, “instruction table 1” and “instruction table 2” are registered in association with the instruction group ID “SG1”, and therefore the data of the plan table 83 is shown in FIG. Expands to two instruction tables 1 and 2.

The instruction table 1 (instruction table 92) and the instruction table 2 (instruction table 93) are, as shown in FIG. 10, lot number, instruction group ID, instruction ID, update date / time, updater ID, start date / time, end date / time, item. It is composed of data indicating quantity and the like .

  For the column for which “master” is set as the storage data category in the instruction expansion detailed definition master 64 in FIG. 5, the data of the target column of the target table associated with the correlation definition master 65 is referred to the reference source table. Store as original column data.

  For example, the storage data classification of “instruction table 1” in the instruction expansion detailed definition master 64 of FIG. 5 is “master”, and in the correlation definition master 65, the column name “item” of “plan table 1” is in the parts master 66. Since it is associated with the column name “item”, the data “I0005” of the column name “item” of the “plan table 1” is referred to as the data of the column name “part” of the “instruction table 1”, and the component master The data “B01” of the column name “part” corresponding to the data data “I0005” of the column name “item” 66 is stored.

  In addition, for the column whose stored data category of the instruction development detailed definition master 64 is “user AP”, the execution result data of the registered user AP is stored as the data of the corresponding column of the corresponding instruction table.

  “User AP” is set as the storage data classification of the column name “part quantity” of the instruction table name “instruction table 1” in the instruction development detailed definition master 64 of FIG. 5, and “part quantity calculation processing” is registered as the execution AP. Therefore, the processing result of the part quantity calculation process is stored as data of the column “part quantity” in the instruction table 1 of FIG.

Next, the instruction output process executed by the instruction output unit 14 will be described with reference to FIGS.
For example, when a specific instruction developed on the Web screen is selected by the user and the instruction output button is operated, the instruction output unit 14 creates an instruction output request queue 101 (see FIG. 11) for the selected instruction. Issued (step S31).

As shown in FIG. 11, the instruction output request queue 101 stores data of function classification, request type, instruction group ID, instruction ID, and lot number.
Next, the registered execution APs are sequentially executed with reference to the information in the instruction output request queue 101 and the engine execution AP master 71 of FIG. 7 (step S32).

  In the engine execution AP master 71 of FIG. 7, the execution AP “instruction output process” is registered in association with the instruction ID “S1”, and the execution AP “instruction output process” and “mail” are associated with the instruction ID “S2”. Notification process "is registered.

  When the instruction output request queue 101 is issued, the execution APs having the function classification of the engine execution AP master 71 of “instruction” and the request type of “output” are executed in order (step S33).

Next, referring to the instruction output definition master 72, the instruction output detailed definition master 73, and the instruction table, the instruction data is created (step S34).
As shown in FIG. 11, the instruction data 1 and 2 (instruction data 102 and 103) are made up of data indicating a lot number, a start date and time, an end date and time, an item, a quantity, and the like .

  In the instruction output detailed definition master 73 in FIG. 7, the correspondence relationship between the data item names of the data set IDs “DS_SendSashizu01” and “DS_SendSashizu02” and the column names of the instruction tables 1 and 2 is defined. According to the definition of the instruction output definition master 73, the data of each column of the instruction tables 1 and 2 are stored in the corresponding columns of the instruction data 1 (instruction data 102) and the instruction data 2 (instruction data 103) in FIG. .

Next, FIG. 12 is a diagram illustrating a data flow of the above-described plan capture, instruction expansion, and instruction output processing.
When the host system stores the plan data 81 in a specific folder, the plan acquisition unit 12 acquires the plan data 81 and executes the execution APs registered in the engine execution AP master 54 in the specified order. Further, the plan table 1 (plan table 83) is created based on the column name, storage data classification, and data item name defined in the acquisition detail definition master 57. Since “transmission” is set as the storage data category for the plan management number, start date / time, end date / time, item, and quantity in the plan table 1, the data in the corresponding column of the plan data 81 received from the host system is displayed. Stored. Since each column of the plan group ID, update date / time, and updater ID is set to “automatic” as the storage data category, the data of those columns is set by the manufacturing execution system.

  In order expansion, execution APs registered in association with the instruction group ID in the engine execution AP master 61 (for example, instruction expansion processing and workflow notification processing) are executed in the specified order. Furthermore, according to the storage data classification of each column defined in the instruction development detailed definition master 64, the data of the execution result of the user AP, the data of the corresponding columns of the parts master 66 and the manufacturing method master 67 are stored in the instruction tables 1 and 2. Stored. Data is automatically set by a manufacturing execution system in a column in which “automatic” is set as the storage data category.

  In the instruction output, the execution APs (for example, the instruction output process) registered in the engine execution AP master 71 in association with the instruction ID are executed in the specified order. Further, the data is stored in the corresponding data item of the instruction data 1 and 2 based on the correspondence between the item name of the data set ID defined in the instruction output detailed definition master 73 and the column name of the instruction tables 1 and 2. The instruction data can be transmitted to the transmission destination system.

According to the first embodiment described above, even if the manufacturing process, manufacturing method, manufactured item, and the like differ depending on the user, the planned capture master (engine execution AP master 54, planned capture detailed definition master 57, etc.) 15 Individual users register data in the instruction development system master (engine execution AP master 61, instruction development detailed definition master 64, etc.) 17 and instruction output system master (instruction output definition master 72, instruction output detailed definition master 73, etc.) 19. and, also, by registering an execution AP to run by referring to data defined in their master can perform total Etokomi, orders deployment, the order output with a common program. This eliminates the need for customizing the plan capture program, the instruction expansion program, the instruction output program, etc. for each user as in the prior art.

  Next, FIG. 13 is a diagram illustrating a configuration of a manufacturing execution system according to the second embodiment of this invention. This second embodiment uses a general-purpose program for processing for events given from different systems such as manufacturing processes, manufacturing processes, etc., or processing for receiving actual data and transmitting the actual data to other systems. It can be realized by using.

The workflow creation unit 111 includes an event management unit 112, an action management unit 113, and a performance management unit 114.
The event management unit 112 performs post-event reception processing, event distribution processing, event transmission processing, and the like with reference to the event-related master table 121 for events received from its own system or other systems. The processing result data is stored in the event database 122.

  The action management unit 113 executes processing for the events distributed by the event management unit 112 with reference to the action system master table 123. When the action activation condition is satisfied, a predefined action execution AP (application) is activated. The processing result data is stored in the action database 124.

  The track record management unit 114 performs post-track data capture processing on track record data received from another system, and stores the processing results in the track record database 125. Further, the performance data is transmitted to another system with reference to the performance system master table 126.

  The manufacturing execution system according to the second embodiment provides an engineering tool for a user to individually define in advance an application to be executed at a timing after event distribution, an action process to be started when an event is acquired, and the like.

FIG. 14 is a diagram showing an event definition screen 131 displayed by the engineering tool for event definition.
In the event definition screen 131 shown in FIG. 14, an event ID, an event name, a batch level indicating whether the event is a procedure, a unit, an operation, or a phase, and record data associated with the event ID can be registered. . In another event definition screen, an event assignment destination, an event transmission destination, a user AP to be executed before and after an event assignment can be registered. The registered data is stored in the event system master 121.

FIG. 15 is a diagram showing an event system definition screen 132 displayed by the engineering tool.
In the event system definition screen 132, for example, when a specific unit ID is selected, a hierarchical event selection screen 133 is displayed. In this hierarchical event selection screen 133, a child event can be added to the parent event. FIG. 15 shows an example in which a child event having an event name “unit 01” is added to the event ID “EVENT01”. The definition result of the event system definition screen 132 is registered in the event system definition master 121.

FIG. 16 is a diagram showing an action definition screen 134 displayed by the engineering tool.
On the action definition screen 134, it is possible to define an action process that is activated when an event is acquired. The definition result of the action definition screen 134 is registered in the action system master 123.

FIG. 17 is a diagram showing an action activation rule definition screen 135 displayed by the engineering tool.
On the action activation rule definition screen 135, activation conditions for the selected action can be defined. When an arbitrary action is selected on the action activation rule definition screen 135, an action activation rule detail definition screen 136 is displayed. On this screen, it is possible to register an activation rule, a user AP that is activated when the activation rule is satisfied, and the like. The definition result of the action activation rule definition screen 135 is registered in the action system master 123.

FIG. 18 is a diagram showing parent process / process registration screens 137 and 138 displayed by the engineering tool.
A parent process / process registration screen 137 shown in FIG. 18 is a display example when a process is registered, and a parent process / process registration screen 138 is a display example when a facility is registered. The registration result is registered in the action system master 123.

FIG. 19 is a diagram showing a record acquisition definition screen 139 displayed by the engineering tool.
On the result fetch definition screen 139, for example, when a stored data column of a specific column of the result table 01 is clicked, a stored data selection screen 140 is displayed. Since the list of item names of registered transmission data is displayed on the stored data selection screen 140, any item name can be selected and registered. The registration result is registered in the performance system master 126.

The processing operation of the workflow creation unit 111 after the event definition, the action definition, the result acquisition definition, and the like are performed as described above will be described.
First, the transmission function, the data conversion function, and the processing operation of the event management unit 112 will be described with reference to FIGS. The transmission function, the data conversion function, and the event management unit 112 are realized as a program module, for example.

  When an event is received from another system or an event is received from the instruction creation unit 11, the transmission function creates a reception event queue 161 (FIG. 21) and passes it to post-event reception processing. The data conversion function refers to the transmission definition master table 151 and the transmission data definition master table 152 in FIG. 20, and stores data in a specified data format in a specified folder.

The event management unit 112 first executes the following post-event reception processing.
The received event data 162 is acquired from the specified folder, and the execution AP master table 154 after receiving the event is searched using the event ID of the received event data 162 as a key. It is determined whether or not it exists (step S111).

When there is data with the “before” classification before and after registration, the application registered in the execution AP column is executed (step S112).
FIG. 20 is a diagram showing an example of the event system master table 121. The event master 121 includes a transmission definition master table 151, a transmission data definition master table 152, an event definition master table 153, an event reception execution master table 154, an event distribution destination master table 155, and an event transmission destination. A master table 156.

The configurations of the transmission definition master 151 and the transmission data definition master 152 are the same as the transmission definition master 51 and the transmission data definition master 52 of FIG.
In the event definition master 153, an event ID, an event name, a batch level, a procedure ID, a device ID, and a parent event ID are registered.

In the example of FIG. 20, it is registered that the parent event of the event ID “UNIT1” is “PROC1”.
In the execution AP master 154 after receiving an event, data indicating an event ID, a pre-registration classification, an activation order, and an execution AP are registered.

In the event assignment destination master 155, an event ID and data indicating the assignment destination are registered.
In the example of FIG. 20, it is registered that the event distribution destination of the event ID “PROC3” is “action reception” and the event distribution destination of the event ID “PROC1” is “event transmission”. By defining the distribution destination in the event distribution destination master 155, it is possible to specify whether action processing or event transmission processing is performed on the received event.

In the event transmission destination master 156, data indicating an event ID and a transmission destination system ID is registered.
For example, when the event ID of the reception event data 162 is “PROC3”, the processing of steps S111 and S112 is performed by searching the execution AP master 154 after event reception shown in FIG. 20 using the event ID “PROC3” as a key. Thus, it is determined whether or not there is data having a “previous” classification before and after registration. In this case, “application 1” and “application 2” are registered in the execution AP master 154 after receiving an event in association with the event ID “PROC3” as execution APs whose registration before and after classification is “previous”. Since “application 1” is the first activation order, “application 2” is executed after “application 1” is executed.

Next, the pre-event distribution queue 163 is created and passed to the event distribution process (step S113).
Next, the event management unit 112 executes the following event distribution process.

The data in the corresponding column of the pre-event distribution queue 163 is stored in the event history management table 164 (FIG. 22) (step S121).
When the pre-event distribution queue 163 as shown in FIG. 21 is created, the event history management table 164 shown in FIG. The event ID, batch level, procedure ID, device ID, lot number, start date / time, end date / time, and data indicating the registration date / time are stored.

  Next, the post-event reception execution AP master 154 is searched using the event ID of the reception event data 162 as a key, and it is determined whether or not there is data having a “post-registration” classification (step S122).

  If there is data having a “after” classification before and after registration, an application whose classification is “after” registered in the execution AP of the execution AP master 154 after event reception is executed (step S123).

  As shown in FIG. 21, when the event ID of the pre-event distribution queue 163 is “PROC3”, the execution AP master 154 after receiving the event is searched by using the event ID “PROC3” as a key by the process of step S122 described above. It is determined whether or not there is data having a “after” classification before and after registration. In this case, since “application 3” is registered as the execution AP whose registration before and after classification is “after”, “application 3” is executed in step 123.

Next, it is determined whether or not the event ID specified in the pre-event distribution queue 163 is registered in the event transfer destination master 155 (step S124).
If the corresponding event ID is registered in the event distribution destination master 155, it is determined whether the distribution destination is “action reception” or “event transmission” (step S125).

  When the distribution destination is “action reception”, the reception action queue 165 is created, and when the distribution destination is “event transmission”, the pre-event transmission queue 166 is created (step S126).

The reception action queue 165 and the pre-event transmission queue 166 shown in FIG. 22 are created by the processing in step S126 described above.
As shown in FIG. 22, the reception action queue 165 stores data indicating an event ID, a batch level, a procedure ID, a lot number, a batch number, an action start date and time, and an end date and time. Further, data similar to the reception action queue 165 is also stored in the pre-event transmission queue 166.

Next, the event management unit 112 executes the following event transmission process.
The pre-event transmission queue 166 is read, the event transmission destination master 156 is searched using the event ID of the pre-event transmission queue 166 as a key, and the corresponding transmission destination system ID is acquired (step S131).

Next, the transmission event data 167 (see FIG. 22) is transmitted to the folder defined in the transmission definition master 151 (step S132).
As shown in FIG. 22, the transmission event data 167 includes data indicating an event ID, a batch level, a procedure ID, a device ID, a lot number, a batch number, a start date and time, and an end date and time.

Through the processing in step S131, the event transmission destination master 156 as shown in FIG. 22 is searched to acquire the transmission destination system ID “SendEvent01”. The transmission definition master 151 and the transmission data definition master 152 are searched using the acquired transmission destination system ID as a key to acquire the transmission destination folder name “F: SendEVENT” and the file name “EVENT.CSV”. Then, the transmission event data 167 of FIG.
Store as “V”.

Next, the processing operation of the action management unit 113 will be described with reference to FIGS.
The action system master 123 includes an action activation AP master table 171, an action activation condition master table 172, and an item check master table 173 shown in FIG.

  In the action activation AP master 171, data indicating a rule number, an action name, and an action execution AP is registered. In the action activation condition master table 172, data indicating rule No, horizontal serial number (AND condition), vertical serial number (OR condition), event ID, start / end classification, and EXIT execution AP are registered.

Registered in the item check master 173 is data indicating rule No, rule No horizontal serial number, rule No vertical serial number, item name, code classification, and value.
The action activation condition master 171 is a table for defining rule establishment conditions and applications to be executed when the rules are established. In the action activation condition master 172 of FIG. 23, “start” is set as the start / end classification of the event IDs “UNIT2a” and “UNIT2b” of rule 1, and the serial numbers “1”, “2” is set, and the same number “1” is set as the longitudinal serial number (OR condition). Since the serial number is set as the AND condition of the event IDs [UNIT2a] and “UNIT2b” and the same number is set as the OR condition, when the AND condition is satisfied, that is, when both start events are received, the rule 1 condition One of the above will be established.

  In the action activation condition master 171 of FIG. 23, “End” is set as the start / end category of the event IDs “UNIT2a” and “UNIT2b” of Rule 1, and “1” and “2” are set as AND conditions thereof. Since both of the OR conditions are set to “2”, one of the conditions of rule 1 is satisfied when both end events of event IDs “UNIT2a” and “UNIT2b” are received.

Then, when the termination condition of the above rule 1 is satisfied, “action AP1” defined in association with rule 1 in the action activation AP master 171 of FIG. 23 is activated.
The condition for establishing rule 2 in the action activation condition master 171 in FIG. 23 is when an end event of “PROC3” is received. Since the item check AP is registered as the EXIT execution AP, the result of the item check AP is The condition is satisfied when it is satisfied.

The action management unit 113 reads the reception action queue 181 (FIG. 24) created by the event distribution process and acquires the event ID (step S141).
Next, referring to the action activation condition master table 172 (FIG. 23), the data registered in association with the event ID is acquired, it is determined whether or not the rule is established, and the action activation management table 182 ( FIG. 24) is created (step S142).

  Here, the processing operation of the action management 113 will be described in the case where a start event with an event ID “UNIT2a” and a start event with an event ID “UNIT2b” shown in FIG. 24 are received.

  In the action activation condition master 172 of FIG. 23, when the establishment condition of “Rule 1” has received both start events of event ID “UNIT2a” and event ID “UNIT2b”, or has received both end events It is defined that

When receiving the reception action queue 181 of the event ID “UNIT2a” shown in FIG. 24, the action management unit 113 stores the data of the reception action queue 181 as “start” as the start / end category and the condition state as the action start management table 182. Data indicating “established” is stored.

  Next, when the reception action queue 183 having the event ID “UNIT2b” shown in FIG. 24 is received, the data of the reception action queue 183 is added to the action activation management table 184 as shown in FIG. ", Data indicating" satisfied "is stored as the condition state.

  At this stage, since two start events “UNIT2a” and “UNIT2b” are received, the condition of “rule 1” of the action activation condition master 172 is satisfied. Since the condition of rule 1 is satisfied, the action management unit 113 executes “action AP1” registered in association with “rule 1” in the action activation AP master 171.

  When the condition of rule 1 is satisfied and the application is executed, the condition states of the event IDs “UNIT2a” and “UNIT2b” in the action management table 185 are rewritten to “execution complete” as shown in FIG.

Next, the results data capture post-processing and results data transmission processing in the results management unit 114 will be described with reference to FIGS.
The actual master 126 includes a transmission definition master table 191, a transmission data definition master table 192, an actual reception management master table 193, an actual data item master table 194, and an actual transmission destination master table 195 illustrated in FIG. 27. And an actual transmission destination detailed definition master table 196.

The data structures of the transmission definition master 191 and the transmission data definition master 192 are the same as the transmission definition master 151 and the transmission data definition master 152 of FIG.
In the record reception management master 193, data indicating a data set ID, an event ID, and a record record management table name is registered.

In the result data item master 194, data indicating the result table name, column name, storage data classification, and data item name of the transmission result data 206 (FIG. 29) is registered.
When the result management unit 114 receives the result data 201 (FIG. 28) from another system, the result management unit 114 creates the reception result queue 202 (FIG. 28) and passes the result data to the post-processing process (step S151).

  The process after fetching actual data consists of the following processes. The record reception management master 193 is searched using the data set ID of the record record queue 202 as a key to acquire the record record management table name and event ID (step S152).

  Next, event data is acquired by searching the event history management table 164 using the acquired event ID and data (lot No., batch No., etc.) in the reception result queue 202 as keys (step S153). The event management table 164 is a table created by event distribution processing, and is the same as the event management table 164 of FIG.

  The acquired data, received record data 201, and record data item master 194 are referred to, the acquired data is stored in the corresponding data item of the record record management table 204, and the record pre-transmission queue 205 is created (step S154). .

Next, the results management unit 114 executes the following results data transmission process.
The record history management table 204 is searched using the event ID of the record pre-transmission queue 205 as a key to obtain the corresponding data (step S161).

  Next, the transmission destination system ID is obtained by searching the actual transmission destination master 195 (FIG. 27) using the data set ID and event ID of the pre-transmission queue 205 as a key (step S162).

  Next, the actual transmission destination detailed definition master 196 is searched by using the transmission destination system ID and the data set ID as keys, and the data item name, the actual table name, and the column name are acquired, and each data item of the transmission actual data 206 is The corresponding data in the result history management table 204 is stored (step S163).

  As a result of the processing in step S163 described above, the “data set ID”, “event ID”, “lot number”,... Registered in the data item name column of the actual transmission detailed definition master 196 in FIG. Is set as the data item name of the transmission result data 206, and the data of the corresponding column of “PROC3 result” in the result history management table 204 is stored in each data item.

FIG. 30 is a diagram showing the flow of processing when an event is received from a lower system and a workflow is created.
When an event, for example, a start event with event IDs “UNIT2a” and “UNIT2b” is received from a lower system (another system), the event management unit 112 refers to the action activation condition master 172 in FIG. It is determined whether one of the above is established. When the condition is satisfied, the action activation AP master 171 in FIG. 23 is referred to, and “action AP1” that is the activation action of rule 1 is activated.

  Further, when receiving the end events of the event IDs “UNIT2a” and “UNIT2b”, the event management unit 112 refers to the action activation condition master 172 and determines whether or not the rule 1 is satisfied. When the rule 1 condition is satisfied, the action activation AP master 171 is referred to activate “action AP1” that is the rule 1 activation action.

  When the record data of the data set ID “PROC3” is received, the record management unit 114 refers to the record reception management master 193 in FIG. 26 and records the record record management table associated with the data set ID. The name “PROC3 results” is acquired. Then, with reference to the actual transmission detailed definition master 196, the data of each column of the actual history management table “PROC3 actual” 204 is acquired, and the data is stored in the corresponding data item of the actual transmission data 206 in FIG. By storing this transmission result data 206 in a folder defined in the transmission definition master 191, transmission of the result data of the event ID “PRPC3” to the other system is completed.

  According to the second embodiment described above, action activation conditions, action programs executed when activation conditions are established in advance in the action system master 123 (action activation condition master 172, action activation AP master 171, etc.), etc. By registering, you can use a common event processing program, event distribution processing program, and action processing program for events that occur from different production methods and production systems in different manufacturing processes. There is no need to customize for each user.

Further, data necessary for the performance system master 126 (the performance reception management master 193, the performance data item master 194, etc.) in advance (correspondence between the result history management table name, the column of the performance history management table and the data item of the transmission performance data) By registering, it is possible to use a common processing program (for example, processing program after fetching actual data, actual data transmission program) for actual data with different specifications for each user. There is no need to customize it.

The manufacturing execution system may include both the manufacturing instruction creation program of the first embodiment and the workflow creation program of the second embodiment.
The data configuration of the master table is not limited to that described in the embodiment, and a part or all of a specific master table may be integrated with another master table. The data structure of the master table is not limited to that shown in the embodiment, and any data structure may be used as long as the program can be shared.

It is a figure which shows the structure of the manufacturing execution system of 1st Embodiment. It is explanatory drawing of a plan taking-in definition. It is a figure which shows a transmission system master and a plan taking-in system master. It is explanatory drawing of an instruction | indication expansion | deployment definition. It is a figure which shows an instruction | indication expansion | deployment type | system | group master. It is explanatory drawing of an instruction | command output definition. It is a figure which shows an instruction | indication output type | system | group master. It is a figure which shows a series / group registration screen. It is a figure which shows plan data, a plan taking-in request queue, and a plan table. It is a figure which shows an instruction | indication expansion | deployment queue | queue and an instruction | indication table. It is a figure which shows an instruction | indication output request queue and instruction data. It is a figure which shows the data flow of plan taking-in, instruction expansion, and instruction output processing. It is a figure which shows the structure of the manufacturing execution system of 2nd Embodiment. It is a figure which shows an event definition screen. It is a figure which shows an event structure definition screen. It is a figure which shows an action definition screen. It is a figure which shows an action starting rule definition screen. It is a figure which shows a parent process / process registration screen. It is a figure which shows a performance acquisition definition screen. It is a figure which shows an event type master. It is a figure which shows reception event data and an event distribution queue. It is a figure which shows an event history management table and a reception action queue. It is a figure which shows an action starting AP master and an action starting condition master. It is a figure which shows a reception action queue and an action starting management table. It is a figure which shows an action starting management table. It is a figure which shows a performance reception management master and a performance item master. It is a figure which shows a performance transmission master and a performance transmission detailed definition master. It is a figure which shows a reception performance queue and a performance history management table. It is a figure which shows transmission performance data. It is a figure which shows the flow of a process when producing a workflow.

Explanation of symbols

DESCRIPTION OF SYMBOLS 11 Instruction production | generation part 12 Plan acquisition part 13 Instruction expansion part 14 Instruction output part 15 Plan acquisition system master table 16 Planning database 17 Instruction expansion system master table 18 Instruction database 19 Instruction output system master 20 Transmission system master table 111 Workflow creation part 112 Event management unit 113 Action management unit 114 Performance management unit 121 Event system master table 123 Action system master table 126 Performance system master table

Claims (4)

A program for performing a manufacturing order in a manufacturing execution system that executes production of a part or product, and the program for performing the manufacturing order performs a program unit that performs plan capture, a program unit that performs order expansion, and an instruction output Has a program part,
The program part that takes in the plan is
Creating a plan capture execution application master definition that associates a plan group ID for specifying production plan data of a part or product with an application executed in plan capture, and storing the definition in the device;
Preliminarily creating a definition of a plan table definition master for associating the plan group ID and the plan table,
Creating in advance a definition of a plan capture detailed definition master that associates a column name of the plan table with a data item name of the production plan data,
Referring to the stored plan capture execution application master and sequentially executing applications registered in association with the plan group ID;
Storing the production plan data and execution result data of the application in a corresponding item of the plan table defined in the stored plan capture detailed definition master and performing plan capture;
Have
The program part for performing the instruction development is:
And storing in the planning group ID as the previously created device definitions Order expanded definition master associating orders group ID,
Creating in advance an instruction development execution application master definition for associating the instruction group ID with an application executed in instruction expansion;
Creating in advance a definition of an instruction table master for associating the instruction group ID with an instruction table;
Creating in advance a definition of an instruction development detailed definition master that associates a plurality of columns of the instruction table with data to be stored in each column;
Obtaining an instruction group ID corresponding to the plan group ID with reference to the stored instruction development definition master;
With reference to said stored orders deployment execution application master, and executing an application that is registered in association with the acquired order group ID sequentially,
The data obtained from the production plan data and the execution result data of the application are stored in the corresponding column of the instruction table defined in the stored instruction expansion detailed definition master, and a plurality of pieces of data for one plan data are stored . Creating an instruction table and expanding the instructions ;
Have
The program unit for outputting the instructions is:
Creating in advance a definition of an instruction output execution application master that associates the instruction group ID with an application executed in the instruction output;
Creating a definition of an instruction output definition master that associates the instruction group ID with a data set ID in advance and storing the definition in the apparatus;
Creating a definition of an instruction output detailed definition master that associates the data item name of the instruction data with the column name of the instruction table, and storing the definition in the apparatus;
Referring to the stored instruction output execution application master and executing an application registered in association with the instruction group ID;
Storing the data of each column of the instruction table and the data of the execution result of the application in a corresponding data item of the instruction data defined in the instruction output detailed definition master and outputting the data to the outside;
Have
A manufacturing order creation program for causing a computer to execute a program section for performing the plan capture, a program section for performing the instruction expanding section, and a program section for performing the instruction output in this order . The instruction expansion detailed definition master is automatically set in the data structure of at least the data of each column of the instruction table by the application execution result data, the production plan data, and the manufacturing execution system. 2. The manufacturing order creation program according to claim 1 , further comprising storage data classification data indicating which data of the data to be stored is stored . In a manufacturing execution system that executes production of parts or products, a manufacturing order creation device that performs a manufacturing order, the manufacturing order creation device having a plan capture unit, an order development unit, and an instruction output unit,
The plan capture unit
A plan group ID that identifies production plan data for parts or products and a definition of a plan capture execution application master that associates an application that is executed in plan capture are created in advance and stored as a plan capture execution application master in the device. 1 storage means;
A second storage means for creating in advance a plan table definition master definition for associating the plan group ID with the plan table and storing it in the apparatus as a plan table definition master;
A third storage means for creating a plan capture detailed definition master definition that associates the column name of the plan table with the data to be stored in each column in advance and storing it in the apparatus as the plan capture detailed definition master;
Corresponding to the plan group ID defined in the plan table definition master stored as the second storage means with reference to the plan capture execution application master stored as the first storage means Execution means for sequentially executing the application registered with the attached,
Plan capture for storing the production plan data and the execution result data of the application in the corresponding column of the plan table defined in the plan capture detailed definition master stored as the third storage means Means,
With
The instruction expanding unit
First storage means for creating a definition of an instruction expansion definition master that associates the plan group ID and the instruction group ID in advance and storing the definition as an instruction expansion definition master in the apparatus ;
A second storage means for creating in advance a definition of an instruction expansion execution application master for associating the instruction group ID with an application executed in instruction expansion, and storing the definition as an instruction expansion execution application master in the apparatus;
A third storage means for creating an instruction table master definition that associates the instruction group ID with the instruction table in advance and storing the definition as an instruction table master in the apparatus;
A plurality of columns of the instruction table, and a fourth storage unit that pre-creates an instruction expansion detailed definition master definition that associates data stored in each column and stores the definition as an instruction expansion detailed definition master in the apparatus;
Obtaining means for obtaining an instruction group ID corresponding to the plan group ID with reference to the instruction development definition master stored as the first storage means;
An execution means for sequentially executing applications registered in association with the instruction group ID acquired by the acquisition means with reference to the instruction expansion execution application master stored as the second storage means;
The production plan data and the execution result data of the application are stored in the corresponding columns of the instruction table defined in the instruction expansion detailed definition master stored as the fourth storage means, and are stored in one plan. Order development means for creating a plurality of instruction tables for data and developing the instructions;
With
The instruction output unit
A first storage means for creating in advance a definition of an instruction output execution application master for associating the instruction group ID with an application executed in the instruction output, and storing the definition as an instruction output execution application master in the apparatus;
A second storage means for creating an instruction output definition master definition that associates the instruction group ID and the data set ID in advance and storing the definition as an instruction output definition master in the apparatus;
A third storage means for creating a definition of an instruction output detailed definition master that associates a data item name of the instruction data with a column name of the instruction table in advance and storing the definition as an instruction output detailed definition master in the apparatus;
Execution means for executing an application registered in association with the instruction group ID with reference to the instruction output execution application master stored as the first storage means;
The data of each column of the instruction table and the data of the execution result of the application are stored in the corresponding data item of the instruction data defined in the instruction output detailed definition master stored as the third storage means. And an instruction output means for outputting to the outside,
A production order creating apparatus comprising: The instruction expansion detailed definition master is automatically set in the data structure of at least the data of each column of the instruction table by the application execution result data, the production plan data, and the manufacturing execution system. 4. The production order creating apparatus according to claim 3, further comprising storage data classification data indicating which data of the data to be stored is stored.