CN119234242A

CN119234242A - Configuration method of production system, electronic equipment and storage medium

Info

Publication number: CN119234242A
Application number: CN202380008924.3A
Authority: CN
Inventors: 邓尚坤; 张立波; 吕明涛; 王洪; 朴南植; 段季芳; 李文娟
Original assignee: BOE Technology Group Co Ltd; Beijing BOE Technology Development Co Ltd; Beijing Zhongxiangying Technology Co Ltd
Current assignee: BOE Technology Group Co Ltd; Beijing BOE Technology Development Co Ltd; Beijing Zhongxiangying Technology Co Ltd
Priority date: 2023-04-28
Filing date: 2023-04-28
Publication date: 2024-12-31
Also published as: WO2024221445A1

Abstract

The disclosure provides a configuration method of a production system, electronic equipment and a storage medium, and relates to the technical field of semiconductor encapsulation systems. The production system comprises a plurality of production devices, the method comprises the steps of creating a recipe for the plurality of production devices according to user input data, wherein each production device is associated with one or more recipes, responding to configuration requests for at least one production device in the plurality of production devices, determining a recipe selection rule applicable to the configuration requests in a plurality of preset recipe selection rules, selecting a recipe matched with the configuration requests in the plurality of created recipes according to the determined recipe selection rules, and configuring the production devices associated with the recipes by utilizing the selected recipe.

Description

Configuration method of production system, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of semiconductor packaging systems, and more particularly, to a method for configuring a production system, an electronic device, a storage medium, and a computer program product.

Background

The production process recipe (recipe) is a file storing production process information, the contents of which may include a plurality of steps in the process, as well as various process parameter values of each step, the duration of the step, and the like. In the semiconductor manufacturing industry, when a product is processed, corresponding recops are generally configured for equipment manually by a person, so that the equipment can finish processing the product according to the content of the recops. However, because the specifications, functions and the like of the produced products are different, the types of the corresponding recas are also different, so that more recas are formed. Therefore, configuration errors are easily caused by manually configuring the device with the record. In addition, manual configuration results in lower work efficiency.

Disclosure of Invention

The present disclosure provides a configuration method of a production system, an electronic device, a storage medium, and a computer program product.

According to an aspect of the present disclosure, there is provided a configuration method of a production system including a plurality of production apparatuses, the method including:

Creating a recipe for a plurality of production devices based on the user input data, wherein each production device is associated with one or more recipes;

in response to a configuration request for at least one of the plurality of production devices, determining a recipe selection rule applicable to the configuration request from a preset plurality of recipe selection rules;

Selecting a recipe matching the configuration request from the created plurality of recipes according to the determined recipe selection rule;

the production equipment associated with each recipe is configured with the selected recipe.

According to an embodiment of the present disclosure, each recipe selection rule has a priority, and determining a recipe selection rule applicable to a configuration request from among a preset plurality of recipe selection rules includes:

extracting recipe query information for at least one production device from the configuration request;

among the plurality of recipe selection rules, the recipe selection rule having the highest priority that matches the recipe query information is determined as the recipe selection rule applicable to the recipe matching request.

According to an embodiment of the present disclosure, each recipe selection rule specifies at least one data item to be compared, and the priority of each recipe selection rule is determined according to the number of data items specified by the recipe selection rule, the greater the number of data items, the higher the priority.

According to an embodiment of the present disclosure, among a plurality of recipe selection rules, determining a recipe selection rule having a highest priority matching the recipe query information as a recipe selection rule applicable to a recipe matching request includes:

Sequentially determining whether the data items designated by each formula selection rule are a subset or a whole set of the data items related to the formula query information according to the order of the priority from high to low;

If the data item specified by the current recipe selection rule is a subset or a complete set of data items related to the recipe query information, then determining that the current recipe selection rule matches the recipe query information, otherwise determining that the current recipe selection rule does not match the recipe query information.

According to an embodiment of the present disclosure, the plurality of recipe selection rules includes a product level selection rule, a process level selection rule, and a process level selection rule, the priority of the product level selection rule being higher than the priority of the process level selection rule, the priority of the process level selection rule being higher than the priority of the process level selection rule.

According to an embodiment of the present disclosure, the data items specified by the product level selection rules include data items related to products, data items related to main processes and sub-processes of the process, data items related to process steps and data items related to recipes,

The data items specified by the process level selection rules include data items related to the main process flow and the sub-process flow of the process, data items related to the process steps, and data items related to the recipe;

The data items specified by the process step selection rules include data items relating to process sub-flows, data items relating to process steps, and data items relating to recipes.

According to an embodiment of the present disclosure, wherein each recipe selection rule specifies at least one data item to be compared, selecting a recipe from the created plurality of recipes that matches the configuration request according to the determined recipe selection rule comprises:

For each recipe, it is determined whether the value in the recipe for each recipe data item defined by the determined recipe selection rule matches the value in the configuration request, and if so, the recipe is determined to be one of the recipes that match the configuration request.

According to an embodiment of the present disclosure, creating a recipe for a plurality of production devices from user input data includes:

Creating at least one recipe packet based on the recipe packet information entered by the user, the recipe packet including packet logic indicating a production facility and a recipe path corresponding to each recipe packet, wherein the recipe path is used to find a recipe in the recipe packet;

adding at least one recipe to the recipe group based on recipe information input by a user for the recipe group;

And determining production equipment and a logic recipe corresponding to each recipe in the recipe group according to the grouping logic of the recipe group, and associating the data model of the recipe with the production equipment and the logic recipe corresponding to the recipe.

According to an embodiment of the present disclosure, at least one of the recipe group and the recipe has an active state for indicating whether the corresponding recipe group or recipe is available.

In accordance with an embodiment of the present disclosure, the method further includes determining whether each recipe to be added is available based on an activation state of the recipe before adding at least one recipe to the recipe group;

Wherein adding at least one recipe to the recipe packet includes adding a recipe available from the at least one recipe to the recipe packet.

According to an embodiment of the present disclosure, the method further includes editing at least one of the recipe group and the recipe according to a user operation, the editing including modifying, deleting, and raising.

According to an embodiment of the present disclosure, at least one of the recipe groupings and the recipes has a frozen state for indicating whether the corresponding recipe grouping or recipe is editable.

According to an embodiment of the present disclosure, the method further includes establishing a data model for each of the plurality of candidate recipes, wherein adding at least one recipe to the recipe group based on recipe information input by a user for the recipe group includes:

from the plurality of candidate recipes, a data model of a candidate recipe that matches the recipe name in the recipe information is selected as a data model of a recipe in the recipe group.

In accordance with an embodiment of the present disclosure, building a data model for each of a plurality of candidate recipes includes, for each candidate recipe,

Importing or creating a data model of the candidate formula from a database;

The frozen state of the data model of the candidate recipe is set to be non-editable according to the freezing operation of the user.

The activation state of the data model of the candidate recipe is set to be available according to the activation operation of the user.

According to an embodiment of the present disclosure, the method further includes, after importing or creating a data model of the candidate recipe from the database,

Responsive to receiving a start editing instruction for the data model of the candidate recipe, starting editing of the data model of the candidate recipe according to an editing operation by a user;

Ending editing the data model of the candidate recipe according to the editing operation of the user in response to receiving the ending editing instruction for the data model of the candidate recipe,

Wherein editing of the data model of the candidate recipe by a user other than the user is prohibited for a period of time after receiving the instruction to start editing and before receiving the instruction to end editing.

According to an embodiment of the present disclosure, the above method further includes:

Storing the operation event in association with the recipe in response to a user operation event for the recipe, wherein the operation event for the recipe includes at least one of creation, editing, cloning, freezing, unfreezing, activation, deactivation, lifting, use of the recipe, and

In response to a query request for a recipe for which a specified operational event occurred, a recipe associated with the specified operational event is determined from among a plurality of stored recipes.

According to another aspect of the present disclosure, there is provided an electronic device comprising a memory and a processor, the memory having stored therein instructions executable by the processor, which when executed by the processor, cause the processor to perform a method for implementing the method as described above.

According to another aspect of the present disclosure, there is provided a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform a method as described above.

According to another aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements a method as described above.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.

Drawings

The drawings are for a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:

FIG. 1 is a flow chart of a configuration method of a production system according to an embodiment of the present disclosure;

FIG. 2 is a flow chart of a method of creating a recipe for a production facility according to an embodiment of the present disclosure;

FIG. 3 is a schematic illustration of an interface for creating recipe groupings in accordance with an embodiment of the present disclosure;

FIG. 4 is a flow chart of a recipe grouping or recipe modification method according to an embodiment of the present disclosure;

FIG. 5 is a flow chart of a recipe activation method according to an embodiment of the present disclosure;

FIG. 6 is a flow diagram of a recipe modeling method according to an embodiment of the present disclosure;

FIG. 7 is a schematic diagram of a recipe packet creation method according to an embodiment of the present disclosure;

FIG. 8 is a flow chart of a method of determining recipe selection rules in accordance with an embodiment of the present disclosure;

FIG. 9 is a schematic configuration diagram of a recipe selection rule according to an embodiment of the present disclosure;

FIG. 10 is a schematic diagram of priority versus parameter factor according to an embodiment of the present disclosure;

FIG. 11 is a schematic diagram of a recipe full lifecycle management, according to an embodiment of the present disclosure;

FIG. 12 is a modeling tool architecture diagram for recipe modeling in accordance with an embodiment of the present disclosure;

FIG. 13 is a block diagram of a user operated platform according to an embodiment of the present disclosure;

FIG. 14 is a business function architecture diagram of a production system according to an embodiment of the present disclosure;

FIG. 15 is a system technology architecture diagram of a production system according to an embodiment of the present disclosure;

fig. 16A and 16B are application architecture diagrams of a production system according to an embodiment of the present disclosure, and

Fig. 17 is a block diagram of an electronic device suitable for implementing a configuration method of a production system in accordance with an embodiment of the present disclosure.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present disclosure more apparent, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present disclosure. It will be apparent that the described embodiments are some, but not all, of the embodiments of the present disclosure. Based on the described embodiments of the present disclosure, all other embodiments that would be apparent to one of ordinary skill in the art without the benefit of this disclosure are within the scope of this disclosure. It should be noted that throughout the appended drawings, like elements are represented by like or similar reference numerals. In the following description, some specific embodiments are for descriptive purposes only and should not be construed as limiting the disclosure in any way, but are merely examples of embodiments of the disclosure. Conventional structures or configurations will be omitted when may lead to confusion in understanding the present disclosure. It should be noted that the shapes and dimensions of the various components in the figures do not reflect the actual sizes and proportions, but merely illustrate the contents of the embodiments of the present disclosure.

Unless defined otherwise, technical or scientific terms used in the embodiments of the present disclosure should be in a general sense understood by those skilled in the art. The terms "first," "second," and the like, as used in embodiments of the present disclosure, do not denote any order, quantity, or importance, but rather are used to distinguish one element from another.

Fig. 1 is a flow chart of a configuration method of a production system according to an embodiment of the present disclosure.

According to an embodiment of the present disclosure, a production system includes a plurality of production devices. The configuration method of the production system may include operations S110 to S140 as shown in fig. 1.

In operation S110, a recipe is created for a plurality of production devices according to user input data, wherein each production device is associated with one or more recipes.

According to embodiments of the present disclosure, the recipe may include parameter information related to the product being produced. For example, the recipe includes parameter information of a product, parameter information of a production apparatus for producing the product, and the like. For example, the recipe may include product type information, product specification information, product production condition information, process type information for the production facility, operating parameter information for the production facility, and the like.

In some embodiments, each production facility corresponds to a recipe when producing a batch of product. For example, production facility A corresponds to a recipe 1 when producing a batch of product a. For another example, production facility B corresponds to recipe 2 when producing a batch of product B. However, it should be noted that since the same production facility may produce different types of products, the same production facility may correspond to multiple recipes, i.e., each production facility may be associated with one or more recipes. For example, production facility C may produce product C and product d, where production facility C corresponds to recipe 3 when producing product C and recipe 4 when producing product d. Thus, both recipe 3 and recipe 4 are associated with production facility C.

In response to a configuration request for at least one of the plurality of production devices, a recipe selection rule applicable to the configuration request is determined among a preset plurality of recipe selection rules in operation S120.

According to an embodiment of the present disclosure, the configuration request is used to determine for which production devices to configure a recipe. For example, related information such as device names of the production device a, the production device B, and the production device C may be included in the configuration request. In some embodiments, the configuration request may also include recipe query information, such as main flow information, sub-flow information, product names, etc., corresponding to the recipe.

In some of these embodiments, the preset plurality of recipe selection rules may include recipe selection rule 1, recipe selection rule 2, recipe selection rule 3, and recipe selection rule 4. The recipe selection rule 2 is selected from the recipe selection rule 1, the recipe selection rule 2, the recipe selection rule 3 and the recipe selection rule 4 as a recipe selection rule suitable for the recipe request according to the relevant information in the configuration request of the production equipment.

In operation S130, a recipe matching the configuration request is selected among the created plurality of recipes according to the determined recipe selection rule.

According to an embodiment of the present disclosure, a recipe selection rule is used to select a recipe from a plurality of recipes that is appropriate for the configuration request. Specifically, the recipe selection rule may include which parameter information is used as a comparison object to select an appropriate recipe. For example, the recipe selection rule a includes a parameter 1 and a parameter 2, which illustrate that the recipe selection rule a selects a recipe suitable for the configuration request from a plurality of recipes with the parameter 1 and the parameter 2 as comparison objects.

In some embodiments, the predetermined formulations may include formulation 1, formulation 2, formulation 3 and formulation 4, and the determined formulation selection rule may be formulation selection rule 2, wherein formulation selection rule 2 includes parameter 1. Selecting a recipe that matches the configuration request among the created plurality of recipes may include selecting a recipe, such as recipe 3, that contains parameter 1 from recipe 1, recipe 2, recipe 3, and recipe 4 as the recipe that is appropriate for the configuration request, with parameter 1 as the comparison object.

It should be noted that each recipe selection rule may include one parameter information or may include a plurality of parameter information. The amount of parameter information is used to characterize which dimensions to conduct recipe screening.

In operation S140, the production equipment associated with each recipe is configured with the selected recipe.

According to embodiments of the present disclosure, recipes are associated with production equipment during creation, and after a recipe matching a configuration request is selected, the production equipment associated with each recipe may be obtained. For example, in some embodiments, the configuration request includes a configuration for production device 1, production device 2, and production device 3, and selecting a recipe that matches the configuration request includes recipe 1, recipe 2, and recipe 3, where recipe 1 is associated with production device 1, recipe 2 is associated with production device 2, and recipe 3 is associated with production device 3. Then the production equipment 1, the production equipment 2 and the production equipment 3 are respectively configured by the formula 1, the formula 2 and the formula 3. In other embodiments, the configuration request includes a configuration for production device 1, production device 2, and production device 3, and selecting a recipe that matches the configuration request includes recipe 1, recipe 2, and recipe 3, wherein recipe 1 is associated with production device 1 and production device 4, recipe 2 is associated with production device 2, and recipe 3 is associated with production device 3. Production equipment 1, production equipment 2, and production equipment 3 are configured with recipe 1, recipe 2, and recipe 3, respectively. Since the configuration request does not include the production apparatus 4, whether to configure the production apparatus 4 with the recipe 1 can be determined according to actual needs. For example, the user can manually operate on the operating platform whether to configure the production device 4.

According to the embodiment of the disclosure, by creating the recipe for the production equipment in advance, when the production equipment needs to be configured, an appropriate recipe selection rule is automatically selected from a plurality of recipe selection rules according to a configuration request input by a user, then a required recipe is selected from the created plurality of recipes according to the determined recipe selection rule, and the production equipment is configured according to the selected recipe. By adopting the mode, the automatic selection and configuration of the formula are realized, the formula is not required to be manually configured for each production equipment by a user, and the problem of configuration errors caused by manual operation is reduced. In addition, the automatic selection and configuration of the formula can also improve the working efficiency.

FIG. 2 is a flow chart of a method of creating a recipe for a production facility according to an embodiment of the present disclosure.

As described in fig. 2, the method of creating a recipe for a production facility of this embodiment includes operations S201 to S206.

At operation S201, at least one recipe packet is created based on recipe packet information input by a user, the recipe packet including packet logic indicating a production device and a recipe path corresponding to each recipe packet, wherein the recipe path is used to find a recipe in the recipe packet.

According to an embodiment of the present disclosure, the recipe group information input by the user may include name information of the recipe group. For example, creating at least one recipe group based on the recipe group information entered by the user may include creating one recipe group based on the name of the recipe group entered by the user, where the recipe group corresponds to a blank file, and the recipe and the production equipment need to be added to the recipe group.

According to embodiments of the present disclosure, recipe groupings may associate generating devices and recipes that are of the same type to the same recipe grouping. For example, production equipment a and production equipment B are used to cut different specifications of products, i.e., all belong to the cutting equipment, respectively, and production equipment a and production equipment B may be associated into the same recipe group.

According to an embodiment of the present disclosure, grouping logic is used to indicate the production equipment and recipe paths to which each recipe group corresponds. In particular, grouping logic is used to indicate which devices the recipe packet corresponds to, e.g., the recipe packet corresponds to a cut class device. The recipe path may include an addressed path for a recipe setting corresponding to a recipe group to facilitate searching for a recipe.

FIG. 3 is a schematic illustration of an interface for creating recipe groupings in accordance with an embodiment of the present disclosure.

As shown in FIG. 3, the operation interface for creating recipe groups includes a recipe group list on the left, a logical recipe list and a production facility list, a recipe list in the middle area and a recipe group on the right. Upon creation of a recipe packet, after entering the operation interface, a "create" button is clicked at the recipe packet in the right area, at which point the recipe packet information, such as the recipe packet name, group owner, version, etc., that needs to be filled out is presented in the operation interface. Clicking the "ok" button after completion of filling completes creation. After the creation of the recipe packet is completed, one piece of recipe packet data is stored in the background, and may be stored in the recipe packet table.

In operation S202, a recipe to be added is determined based on recipe information input by a user for a recipe group.

According to embodiments of the present disclosure, recipe information may include any information that enables searching for a recipe. For example, the recipe information may include attribute information for the recipe. More specifically, the recipe information may include information of a recipe name, a recipe number, and the like.

According to the embodiment of the disclosure, the recipe information may be information directly input by a user, or may be recipe information displayed in a recipe list displayed on a display interface.

According to embodiments of the present disclosure, a data model needs to be built for multiple candidate recipes before creating a recipe group. Determining the recipe to be added based on the recipe information entered by the user for the recipe group includes selecting, from the plurality of candidate recipes, a data model of the candidate recipe that matches the recipe name in the recipe information as a data model of the recipe in the recipe group.

According to an embodiment of the present disclosure, building a data model for a candidate recipe includes importing or creating a data model of the candidate recipe from a database, and setting a freeze state of the data model of the candidate recipe to be non-editable according to a freeze operation of a user. The activation state of the data model of the candidate recipe is set to be available according to the activation operation of the user.

According to an embodiment of the present disclosure, the method further includes starting editing of the data model of the candidate recipe according to the editing operation of the user in response to receiving a start editing instruction of the data model of the candidate recipe after importing or creating the data model of the candidate recipe from the database, and ending editing of the data model of the candidate recipe according to the editing operation of the user in response to receiving an end editing instruction of the data model of the candidate recipe, wherein editing of the data model of the candidate recipe by other users than the user is prohibited for a period of time after receiving the start editing instruction and before receiving the end editing instruction.

In operation S203, it is determined whether each recipe to be added is available according to the activation state of the recipe. In the case where it is determined that the recipe to be added is not available, operation S204 is performed, and in the case where it is determined that the recipe to be added is available, operation S205 is performed.

According to embodiments of the present disclosure, only formulas in an active state can be added to a formula group.

According to embodiments of the present disclosure, after the recipe grouping and recipe editing is completed, the information may be frozen. The recipe groupings and recipes being frozen indicate that the recipe grouping information and recipe information are frozen, cannot be edited again, and cannot be deleted. By the freezing operation, the already issued recipe information can be prevented from being tampered with.

According to embodiments of the present disclosure, the recipe information after freezing may be activated by an activation operation so that an operator may create and use the recipe in a production system.

In operation S204, an unavailable recipe is activated using the activation operation, and then operation S205 is performed.

In operation S205, a recipe available among at least one recipe is added to the recipe group.

In operation S206, the production equipment and the logical recipe corresponding to each recipe in the recipe group is determined according to the grouping logic of the recipe group, and the data model of the recipe is associated with the production equipment and the logical recipe corresponding to the recipe.

According to embodiments of the present disclosure, a logical recipe may be used to address a recipe, i.e., a data model of a recipe may be found from the logical recipe. It should be noted that a data model needs to be built for each recipe before creating a recipe packet.

According to the embodiment of the disclosure, by creating the recipe grouping, the production equipment and the recipe with similarity are conveniently related to the same recipe grouping, and the recipe screening efficiency can be further improved when the production equipment is configured.

According to an embodiment of the present disclosure, editing may further include a freeze operation, a cancel freeze operation, an activate operation.

According to an embodiment of the present disclosure, when a recipe group or recipe is modified, as shown in fig. 3, the information may be modified by clicking a "modify" button while the recipe group is in an editable state.

Fig. 4 is a flow chart of a recipe grouping or recipe modification method according to an embodiment of the present disclosure.

As shown in fig. 4, the modification method of this embodiment includes operations S401 to S408.

In operation S401, an activation state, a freeze state, and an edit state of a recipe group or recipe are acquired in response to a modification request of the recipe group or recipe by a first user.

In operation S402, it is determined whether the activated state is an inactivated state. Operation S403 is performed in the case where it is determined that the activated state is the inactivated state, and operation S407 is performed in the case where it is determined that the activated state is the activated state.

In operation S403, it is determined whether the frozen state is unfrozen. Operation S404 is performed in the case where it is determined that the frozen state is frozen, and operation S405 is performed in the case where it is determined that the frozen state is not frozen.

In operation S404, the frozen state is switched to the unfrozen state, and then operation S405 is performed.

In operation S405, it is determined whether the editing state is in editing. Operation S406 is performed in the case where the editing state is in editing, and operation S408 is performed in the case where the editing state is not in editing.

In operation S406, it is determined whether the first user is a current user. Operation S408 is performed in the case where the first user is the current user, and operation S407 is performed in the case where it is determined that the first user is not the current user.

In operation S407, the first user is not allowed to modify the recipe groupings or recipes.

In operation S408, the first user is allowed to modify the recipe groupings or formulations.

According to an embodiment of the present disclosure, the edit status of a recipe group or recipe is managed using a "frozen status" field, which when the edit status is "in-edit status", indicates that a user is editing. If the accounts of the editor and the current operator are inconsistent, the current information cannot be edited, so that a plurality of users can be prevented from editing the formula group or the formula at the same time, and the production safety problem caused by tampering of the published formula group or formula is avoided.

According to the embodiment of the disclosure, when deleting the recipe group or the recipe, in response to the operation of clicking a 'remove' button, the activation state and the freezing state of the recipe group data are checked, if the recipe group data are in the freezing state, deletion is not allowed, if the recipe group data are in the non-freezing state, deletion is allowed, and a deleting operation is executed in the background.

According to the embodiment of the disclosure, when the formula group or the formula is lifted, the display box is popped up in response to right click operation, and the lifting of the formula group is completed in response to the operation of 'lifting' in the selected display box and the operation of 'yes' in prompt information. It should be noted that, before the version up, the system checks the activation state of the data, and if the data is not in the activation state, the version up is not allowed.

According to the embodiment of the disclosure, when the formula group or the formula is frozen, the display box is popped up in response to right click operation, and the freezing of the formula group is completed in response to the freezing in the selected display box and clicking the yes operation in prompt information. After the user clicks the freeze operation, the system checks the frozen state of the data, and if the frozen state is not the non-frozen state, the system does not allow the freezing, and if the frozen state is the non-frozen state, the system checks the edit state. If the editing state is not edited, the recipe can be frozen, and if the editing state is in the editing process, whether the recipe is the current user or not is checked. Freezing is allowed if the current user, and not allowed if not.

According to the embodiment of the disclosure, when the formula group or the formula is unfrozen, the display box is popped up in response to right click operation, and the unfrozen operation of the formula group is completed in response to the 'non-freezing' operation in the selected display box and the 'yes' operation in prompt information is clicked. After the user clicks to cancel the freezing operation, the system checks the freezing state of the data first, if the freezing state is not the freezing state, the freezing is not allowed to be canceled at the moment, if the freezing state is the freezing state, the user can click to cancel the freezing operation, and the freezing operation is finished, and the state of the recipe group or the recipe is changed to the non-freezing state.

According to the embodiment of the disclosure, when the formula group or the formula is activated, the display box is popped up in response to the right click operation, and the formula group is activated in response to the activation in the selected display box and the yes operation in the prompt message is clicked. After the user clicks the activation operation, the system checks the frozen state of the data, if the frozen state is not the frozen state, the activation is not allowed at this time, and if the frozen state is the frozen state, the user can click the activation to complete the activation operation.

Fig. 5 is a flow chart of a recipe activation method according to an embodiment of the present disclosure.

As shown in fig. 5, the activation method of this embodiment includes operations S501 to S506.

In operation S501, the user may perform recipe information modeling at the modeling tool by batch importation or manually.

In operation S502, the created recipe information is set to a frozen state.

In operation S503, an activation application is acquired in response to an activation operation of recipe information by a user.

In operation S504, the auditor performs approval of the activation application through the production operation platform.

In operation S505, the application approval passing is activated.

In operation S506, the recipe information is activated to allow the user to use the recipe information.

According to the embodiment of the disclosure, by introducing the signing mechanism, when the activation operation is performed, the appointed personnel is required to confirm that the activation is successful, the prescription information issued to the production system is ensured to be approved, and the approval information is recorded, so that the online data is safer and more reliable.

According to the embodiment of the disclosure, in the case of needing to modify an already released recipe, recipe information can be edited in a recipe version-up and recipe cloning mode according to business requirements.

According to embodiments of the present disclosure, one recipe editing method employs a recipe upscaling approach. The method specifically comprises the steps of updating a recipe version in recipe information after the recipe information is edited, storing the recipe information after the recipe version is updated as new-version recipe information, storing the recipe information before the editing as old-version recipe information, and setting the old-version recipe information to be inactive in response to the new-version recipe information being activated. The editing method needs to carry out edition lifting on the original formula information, and the content of the formula information after edition lifting is consistent with the original formula information except for the edition number. At the moment, the new recipe information version can be edited, and after the edition is completed, the new recipe information is frozen and then activated.

According to an embodiment of the present disclosure, another specification editing method employs a version cloning approach. The method specifically comprises the steps of generating a copy of the recipe information before editing the recipe information, and modifying the recipe name in the copy to be different from the recipe name in the recipe information, wherein the recipe information is edited through an editing copy, so that new recipe information is obtained. The editing method is to create new recipe information based on the recipe information, i.e. clone the recipe information, wherein the cloned recipe information has the same content as the original content except the name. The user can edit, freeze and activate the cloned recipe information and manage the cloned recipe information as a new recipe after activating the cloned recipe information.

It should be noted that, the recipe information is edited by using the ways of recipe upgrading and recipe cloning, which will not affect the recipe being used online.

Fig. 6 is a flow diagram of a recipe modeling method according to an embodiment of the present disclosure.

According to the embodiment of the disclosure, the recipe modeling can be performed by an import manner or a new manner, wherein the import manner can edit, modify, freeze, activate and the like the imported recipe, and the new recipe can be edited, modified and frozen by adopting the new manner.

As shown in fig. 6, the recipe modeling method of this embodiment includes operations S610 to S670.

In operation S610, entry into the recipe base data modeling flow is started in response to the recipe creation operation of the first user.

In operation S620, the recipe modeling is performed in a newly built manner. When the user performs recipe modeling in a newly built manner, editing or modifying operations S640 and freezing operations S650 may be performed.

In operation S630, the recipe modeling is performed using the import method. When the user performs recipe modeling in the import manner, editing or modifying operation S640, freezing operation S650, and activating operation S660 may be performed.

In operation S670, the creation ends.

Among them, the editing or modifying operation S640 includes operations S641 to S646.

In operation S641, an editing or modifying operation is entered.

In operation S642, it is determined whether the frozen state is a non-frozen state. In the case where it is determined that the frozen state is not frozen, operation S643 is performed, and in the case where it is determined that the frozen state is frozen, operation S670 is performed.

In operation S643, it is determined whether the editing state is in editing. Operation S644 is performed in the case where it is determined that the edit status is in editing, and operation S670 is performed in the case where it is determined that the edit status is not in editing.

In operation S644, it is determined whether the first user is a current user. Operation S645 is performed in the case where it is determined that the first user is the current user, and operation S646 is performed in the case where it is determined that the first user is not the current user.

In operation S645, the recipe information is edited or modified, and then a freezing operation S650 is performed.

In operation S646, editing or modifying the recipe information is not allowed.

The freezing operation S650 includes operations S651 to S653.

In operation S651, the freezing operation is entered.

In operation S652, it is determined whether the frozen state is a non-frozen state. In the case where it is determined that the frozen state is not frozen, operation S653 is performed, and in the case where it is determined that the frozen state is frozen, operation S670 is performed.

In operation S653, the frozen state of the recipe is changed to frozen.

The frozen recipe may be activated by an activation operation S660, the activation operation S660 including operations S661 to S663.

In operation S661, an activation operation is entered.

In operation S662, it is determined whether the frozen state is frozen. In the case where it is determined that the frozen state is frozen, operation S663 is performed, and in the case where it is determined that the frozen state is non-frozen, operation S670 is performed.

In operation S663, the recipe is changed to an active state.

According to the embodiment of the disclosure, after the recipe is edited or modified, the recipe information can be solidified through freezing operation, cannot be edited again and cannot be deleted, and through the operation, the published recipe information can be prevented from being tampered. In addition, the frozen recipe information may be activated by an activation operation and released so that an operator may use the recipe in the production system.

According to an embodiment of the present disclosure, the editing operation further includes editing of the logical recipe and editing of the grouping logic. Editing of logic formulas and editing of grouping logic are similar to editing of formulas and grouping of formulas, and also comprise operations of modification, deletion, edition lifting, freezing cancellation, activation and the like. The editing of the logic recipe and the editing of the grouping logic are different from the grouping of the recipes and the recipe in that the related information of the logic recipe is stored in a logic recipe table, and the related information of the grouping logic is stored in a stored logic table.

Fig. 7 is a schematic diagram of a recipe packet creation method according to an embodiment of the present disclosure.

As shown in FIG. 7, when a recipe packet is created, a recipe module modeling is first entered to enable a system to model and maintain a recipe, then, recipe packet basic data modeling, recipe packet basic data maintenance and recipe packet data basic data management are sequentially performed, wherein the recipe packet basic data modeling comprises a recipe packet name, a group owner and a group version, then, the system judges whether equipment data is in an activated state or not when the created recipe packet is required to be associated with production equipment, if the equipment data is not in an activated state, the equipment-recipe packet basic data management is performed to associate the production equipment in the recipe packet, wherein the equipment-recipe packet basic data comprises a recipe packet name, an equipment name and a version, then, logic recipe packet modeling, logic recipe packet maintenance and logic recipe packet data management are sequentially performed, wherein the logic recipe packet modeling comprises a recipe packet name, a logic recipe packet name and a version, and then, the system associates a recipe in the recipe packet, judges whether the recipe is in the activated state or not, if the equipment data is in the created recipe packet, the configuration is ended, and the basic data modeling, the basic recipe packet basic data maintenance and the basic recipe packet management are sequentially performed, wherein the equipment-recipe packet basic data management comprises a recipe packet name, a logic recipe packet name and a logic recipe packet name.

It should be noted that, one recipe may be included in the recipe group, or a plurality of recipes may be included.

According to an embodiment of the present disclosure, each recipe selection rule has a priority, each recipe selection rule specifying at least one data item to be compared, the priority of each recipe selection rule being determined according to the number of data items specified by the recipe selection rule, the higher the number of data items, the higher the priority.

According to embodiments of the present disclosure, the data items may be information of factory parameters, product parameters, process parameters, and the like. For example, the data item may be a factory name, a product version, a main flow version, a sub-flow, a flow version, a process step, and the like.

In one embodiment, the data items included in the recipe selection rule a include the data item 1, and the data items included in the recipe selection rule B include the data item 1 and the data item 2, and then the priority of the recipe selection rule B may be considered to be higher than the priority of the recipe selection rule a. It will be appreciated that the larger the number of data items, the more screening conditions are included and therefore the higher the accuracy of the screened formulation.

According to the embodiment of the disclosure, the number of the data items is used as the setting standard of the priority, so that as many data items as possible can be compared in the formula screening process, and the screening accuracy is further improved.

Fig. 8 is a flowchart of a method of determining recipe selection rules according to an embodiment of the present disclosure.

As shown in fig. 8, the method of determining the recipe selection rule of this embodiment includes operations S801 to S805.

In operation S801, recipe query information for at least one production device is extracted from a configuration request.

According to embodiments of the present disclosure, the recipe query information may include, for example, main flow information, sub-flow information, product names, product versions, process steps, and the like, corresponding to a recipe.

In operation S802, it is determined whether the data items specified by the current recipe selection rule are a subset or a complete set of data items related to the recipe query information in order of priority from high to low. Operation S803 is performed in the case where it is determined that the data item specified by the current recipe selection rule is not a subset or a complete set of data items related to the recipe query information, and operation S804 is performed in the case where it is determined that the data item specified by the current recipe selection rule is a subset or a complete set of data items related to the recipe query information.

According to an embodiment of the present disclosure, the recipe selection rules are matched sequentially in order of priority from high to low. For example, recipe selection rule A includes data item 1, data item 2, and data item 3, and recipe selection rule B includes data item 1 and data item 2. Since the priority of the recipe selection rule a is higher than that of the recipe selection rule B, the recipe selection rule a is preferentially matched. It should be noted that, if the matching between the formula matching rule a and the formula query information is successful, the matching between the formula matching rule B is not needed.

By setting the priority and sequentially matching the formula selection rules according to the order of the priority from high to low, the follow-up matching is not needed after the formula selection rules with high priority are successfully matched, and the screening efficiency is further improved.

According to embodiments of the present disclosure, determining whether the data items specified by the current recipe selection rule are a subset or a complete set of data items related to the recipe query information may include, for example, determining whether the data items specified by the current recipe selection rule all belong to the data items related to the recipe query information. For example, the recipe query information includes data item 1, data item 2, and data item 3, the recipe selection rule A includes data item 1 and data item 2, the recipe selection rule B includes data item 1, data item 2, and data item 3, and the recipe selection rule C includes data item 2, data item 3, and data item 4. Since the data item 1 and the data item 2 specified in the recipe selection rule a belong to the subset of the data item 1, the data item 2, and the data item 3 to which the recipe query information relates, the recipe selection rule a matches the recipe query information. Since the data item 1, the data item 2, and the data item 3 specified in the recipe selection rule B belong to the complete set of the data item 1, the data item 2, and the data item 3 to which the recipe query information relates, the recipe selection rule B matches the recipe query information. Since the data items 1,2, and 3 to which the recipe query information relates do not contain the data item 4 specified in the recipe selection rule C, the recipe selection rule C matches the recipe query information.

In operation S803, it is determined that the current recipe selection rule does not match the recipe query information.

In operation S804, it is determined that the current recipe selection rule matches the recipe query information.

In operation S805, the recipe selection rule having the highest priority that matches the recipe query information is determined as the recipe selection rule applicable to the recipe matching request.

According to the embodiment of the disclosure, as described above, the recipe selection rule a and the recipe selection rule B are both matched with the recipe query information, and the recipe selection rule B is taken as a recipe selection rule applicable to the recipe matching request because the recipe selection rule B contains more data items, i.e., has a higher priority than the recipe selection rule a.

According to the embodiment of the disclosure, the recipe screening is further optimized by setting the priority and selecting the recipe selection rule with the highest priority so that the recipe can be screened with the highest accuracy possible.

According to an embodiment of the present disclosure, wherein each recipe selection rule specifies at least one data item to be compared, selecting a recipe from among the created plurality of recipes that matches the configuration request according to the determined recipe selection rule includes determining, for each recipe, whether a value of each recipe data item defined by the determined recipe selection rule in the recipe matches a value in the configuration request, and if so, determining the recipe as one of the recipes that matches the configuration request.

According to an embodiment of the present disclosure, after a recipe selection rule matching a configuration request is determined, a recipe matching the configuration request is screened from a plurality of recipes using the determined recipe selection rule.

In some of these embodiments, the recipe selection rule that matches the configuration request is a recipe selection rule A, and the recipe selection rule A specifies data item 1, e.g., a product name, and data item 2, e.g., a main flow name, into which the product name and the main flow name are entered. Determining whether each of the recipe data items defined by the determined recipe selection rule matches the value in the recipe with the value in the configuration request may include determining whether the data item 1, e.g., product name, and the data item 2, e.g., main flow name, specified by the recipe selection rule a matches the product name, main flow name, contained in the configuration request.

According to the embodiment of the disclosure, the formula selection rule adopts three modes of a product level selection rule, a process level selection rule and a process level selection rule to carry out production and formula configuration, and in the production process of the product, the proper formula information is recommended according to the first order of production to carry out production control, so that the production efficiency is improved, and the product yield is improved.

According to an embodiment of the present disclosure, the data items specified by the product level selection rule include data items related to a product, data items related to a main process and a sub-process of a process, data items related to a process step, and data items related to a recipe, the data items specified by the process level selection rule include data items related to a main process and a sub-process of a process, data items related to a process step, and data items related to a recipe, and the data items specified by the process level selection rule include data items related to a sub-process of a process step, data items related to a process step, and data items related to a recipe.

According to embodiments of the present disclosure, data items regarding a product may include, for example, a product name, a product version, data items regarding a main process and a sub-process of a process may include, for example, a main process version, a sub-process, and a sub-process version, data items regarding a process may include, for example, a process step, and data items regarding a recipe may include, for example, a recipe group, and a logical recipe.

Fig. 9 is a schematic configuration diagram of a recipe selection rule according to an embodiment of the present disclosure.

As shown in fig. 9, the configuration selection rules include a product level selection rule, a process level selection rule, and a process level selection rule. The product level selection rules can comprise factories, products, product versions, main processes, main process versions, sub-processes, sub-process versions and process steps, the process level selection rules can comprise factories, main processes, main process versions, sub-processes, sub-process versions and process steps, and the process level selection rules can comprise factories, sub-process versions and process steps.

According to an embodiment of the present disclosure, the basic information for creation of the product level recipe selection rule includes a product name, a product version, a main flow name, a main flow version, a sub-flow name, a sub-flow version, a factory version, a recipe name, and a recipe version. The creation flow and the editing flow of the product-level recipe selection rule are similar to the creation flow and the editing flow of the recipe, and the embodiments of the present disclosure are not repeated.

According to the embodiment of the disclosure, in the actual production process, if the product, the flow and the process step meet the requirements, the corresponding recipe selection rule is entered to recommend corresponding equipment, recipe groups and recipes. At this time, the user can manually select a proper formula according to the actual situation, so that the efficiency of producing and selecting the formula is improved, and if only a unique formula is found under the formula selection rule, the equipment can adopt the corresponding formula.

According to the embodiment of the disclosure, when the production and manufacture are in an inbound operation, the system can optimize parameters according to parameters provided by current production, and the configuration of 16 parameters is supported in the current formula selection rule, and the parameters are invalid. When the system selects, the system firstly carries out filtering, then filters the obtained parameters, then carries out main parameter and auxiliary parameter division on the parameters, preferentially matches the main parameters, if the main parameters can be matched, the system continues to match the auxiliary parameters until the formula selection rules met by the system are found, if the main parameters cannot be matched, the system directly matches the auxiliary parameters until the formula selection rules met by the system are found.

Fig. 10 is a schematic diagram of priority versus parameter factor according to an embodiment of the present disclosure.

As shown in fig. 10, the relationship between the priority of the recipe selection rule and the number of parameter factors such as the relative step information and the product flow can be described by the following formula (1). y=kx+bx is less than or equal to 16y= c x >16; (1)

Wherein k is the slope of the linear relationship, x represents the number of parameter factors of the recipe selection rule, and y represents the priority level. It will be appreciated that for a determined slope k, the smaller x, the smaller y, the lower the priority level. For example (x < 16), for y1< y2, the priority satisfying kx1+b=y1 is lower than the priority satisfying kx2+b=y2. When x >16, the priority is no longer changing.

According to an embodiment of the present disclosure, the method further includes storing an operation event associated with the recipe in response to an operation event of the recipe by a user, wherein the operation event of the recipe includes at least one of creation, editing, cloning, freezing, unfreezing, activation, deactivation, lifting, and use of the recipe, and determining the recipe associated with the specified operation event among the stored plurality of recipes in response to a query request for the recipe for which the specified operation event occurred.

According to the embodiment of the disclosure, through full life cycle recording of the operation event of the recipe, the corresponding recipe information can be screened according to the requirement, so that the recipe can be tracked and managed conveniently.

According to an embodiment of the present disclosure, the production system is a production system for semiconductor encapsulation. The generating system can adopt an MES manufacturing execution system, wherein MES is Manufacturing Execution System, and the MES is a production informatization management system facing to an execution layer of a workshop of a manufacturing enterprise. Recipe management may employ a recipe management system (RMS, recipe Managemnet Syatem), an RMS is a set of systems used to manage recipes in the semiconductor industry and to guide production and prevent misuse or misuse during production.

According to the embodiment of the disclosure, the formula management system can also realize the full life cycle management of the formula information data, and consists of four stages of analysis, design, system use and system maintenance.

1. Analysis

Analysis, also called investigation and analysis of demand business, is the first key stage of the full life cycle of the recipe and is the most important link. The task of analyzing the period includes determining the type of recipe function, specifying the total goal that must be accomplished, and determining the post-production manufacturing feasibility, which is not embodied in the system function. The analysis period is typically further divided into three parts, namely category of recipe, function, analysis validation defined. The main task of this stage is to determine if the designed recipe meets the production and manufacturing requirements, if the repeatability and subsequent expansibility are good, if the design objective of the information recipe is not known, try to design the recipe, and develop an information management system, which is obviously blind, only wasteful of time and money. The requirement analysis stage is therefore an essential element in the complete life cycle of the formulation.

2. Design and maintenance

Design is another important stage in the overall life cycle of a formulation. The main purpose of the design is to establish a data base for the next stage of system application. The design includes two aspects, namely, the formulation design, wherein the task of the formulation design is to provide formulation integration data which is reliable in production and manufacture, and the main content includes types, functions and defined divisions. Secondly, the system is designed in detail, and the task of the system design embodies the recipe data management. Each functional module for managing the base data of the record is designed, the stage is closely related to the development function of the information system, and the formula, the formula group and the logic formula management module are designed, and the relation among the functional modules is detailed in the formula creation and activation flow.

3. Application of

System application is the most critical stage of the new system. All the work is aimed at production and manufacture, and only a system which meets the production requirement can be counted as an analysis design stage to reach the standard. The application refers to that the result of the system design stage is realized on a computer, so that the production and manufacturing control is realized, the productivity is improved, and the yield of the produced and manufactured products is improved. This stage involves a detailed usage record of the recipe.

4. Maintenance and disposal

Maintenance is a long and laborious task after the formulation is put into normal operation. The main task of the maintenance period is to have the recipe permanently meet the needs of the user. In particular, the tasks of recipe maintenance include correction when the system finds an error during use, modification of the corresponding version of the recipe to meet new production conditions to accommodate new environments when the environment changes, and timely improvement of recipe-related data to meet production needs when the enterprise has new product and process needs. Each maintenance activity is essentially a compressed and simplified recipe definition to the point of application, which involves maintenance update records for the recipe.

The life cycle of the recipe is repeatedly performed, one recipe is continuously updated to the application problem after being designed, analysis is needed again to a certain extent, whether the recipe can meet the current service requirement or not can not meet the system production requirement after frequent maintenance update, and at the moment, the abandonment of the recipe is considered, and a new life cycle is started from new analysis to design a new recipe.

According to the embodiment of the disclosure, the analysis, design, verification and approval of the recipe can comprise filling in the market demand of the recipe in a demand interface, clicking analysis, filling in analysis results, designing a corresponding recipe according to the analysis results, clicking verification to verify the design version of the recipe, clicking an approval button to enter a recipe approval state after the verification results are passed, and actually maintaining the recipe in the system after the approval results are passed.

FIG. 11 is a schematic diagram of recipe full lifecycle management, according to an embodiment of the present disclosure.

As shown in FIG. 11, the full life cycle of a recipe may include key nodes for analysis, recipe design, recipe verification, recipe modeling, recipe configuration, recipe application, recipe maintenance, recipe disposal, and the like. The method can be applied to a signature verification system, a modification activation control system and a production control system in the whole life cycle of the formula. The records of all events for a full lifecycle of a recipe may include a recipe requirement analysis event record, a recipe requirement review event record, a recipe requirement design event record, a recipe verification event record, a recipe modeling event record, a recipe new event record, a recipe modification event record, a recipe clone event record, a recipe freeze event record, a recipe undo freeze event record, a recipe activate event record, a recipe undo activate event record, a recipe escalation audit event record, a recipe use event record, and a recipe discard audit event record.

The recipe demand analysis event record includes that when the system is in demand analysis data, the background write data eventtype is record, typename is none, eventname is analysis, eventdate is current time, createuser is current login user, createdate is current time, and eventID system automatically generates LASTEVENTID to be empty.

The recipe demand review event record includes that when the system is reviewing data, the background write data eventtype is record, typename is recipename, eventname is create, eventdate is current time, createuser is current login user, createdate is current time, and eventID system automatically generates LASTEVENTID a last event ID.

The recipe demand design event record includes that when the system is in demand design data, the background write data eventtype is record, typename is recipename, eventname is design, eventdate is current time, createuser is current login user, createdate is current time, and eventID system automatically generates LASTEVENTID to be last event ID.

The recipe verification event record includes that when the system verifies the recipe data, the background write data eventtype is record, typename is recipename, eventname is verify, eventdate is current time, createuser is current login user, createdate is current time, and eventID system automatically generates LASTEVENTID to be last event ID.

The recipe modeling event record includes that when the system is modeling data, the background writing data eventtype is record, typename is recipename, eventname is modeling, eventdate is current time, createuser is current login user, createdate is current time, and eventID system automatically generates LASTEVENTID to be last event ID.

The new event record of the formula comprises that when the system is newly added with data, background writing data eventtype is record, typename is recipename, eventname is create, eventdate is current time, createuser is current login user, createdate is current time, and eventID system automatically generates LASTEVENTID to be last event ID.

The recipe modification event record includes that when the system modifies the data, the background write data eventtype is record, typename is recipename, eventname is modification, eventdate is current time, createuser is current login user, createdate is current time, eventID system automatically generates LASTEVENTID a last event ID.

The recipe clone event record includes that when the system is cloning data, the background write data eventtype is record, typename is recipename, eventname is copy, eventdate is current time, createuser is current login user, createdate is current time, and eventID system automatically generates LASTEVENTID to be last event ID.

The recipe freeze event record includes that when the system freezes data, the background write data eventtype is record, ypename is recipename, eventname is forzen, eventdate is current time, createuser is current login user, createdate is current time, and eventID automatically generates LASTEVENTID as last event ID.

The recipe undo freeze event record includes that when the system undoes the freeze data, the background write data eventtype is recope, typename is recipename, eventname is unforzen, eventdate is the current time, createuser is the current login user, createdate is the current time, and eventID automatically generates LASTEVENTID the last event ID.

The recipe activation event record includes that when the system activates data, the background write data eventtype is record, typename is recipename, eventname is active, eventdate is current time, createuser is current login user, createdate is current time, and eventID system automatically generates LASTEVENTID as last event ID.

The recipe upgrade event record includes that when the system is in the version up data, the background write data eventtype is recope, typename is recipename, eventname is addversion, eventdate is the current time, createuser is the current login user, createdate is the current time, and eventID automatically generates LASTEVENTID as the last event ID.

The recipe upgrade audit event record includes that when the system is in the upgrade audit data, the background write data eventtype is recope, typename is recipename, eventname is addversionapporve, eventdate is the current time, createuser is the current login user, createdate is the current time, and eventID automatically generates LASTEVENTID as the last event ID.

The formula discard audit event record comprises that when the system discards audit data, the background write data eventtype is recope, typename is recipename, eventname is deleteapporve, eventdate is current time, createuser is current login user, createdate is current time, and eventID automatically generates LASTEVENTID to be last event ID. When the system discards the data, the background writing data eventtype is record, typename is recipename, eventname is delete, eventdate is current time, createuser is current login user, createdate is current time, and eventID automatically generates LASTEVENTID a last event ID.

The recipe usage event record includes that when the system uses the data, the background write data eventtype is record, typename is recipename, eventname is using, useID is the production lot operation history data ID (which can be associated with the current production data) when in use, eventdate is the current time, createuser is the current login user, createdate is the current time, and eventID automatically generates LASTEVENTID is the last event ID.

According to embodiments of the present disclosure, configuration data event records and deconfiguration data event records may also be included.

The configuration data event record includes that when the system is in configuration data, the background writing data eventtype is record, typename is recipename, eventname is policysetup, eventdate is current time, createuser is current login user, createdate is current time, and eventID automatically generates LASTEVENTID as last event ID.

The cancel configuration data event record includes that when the system cancels configuration data, the background write data eventtype is record, typename is recipename, eventname is deletepolicysetup, eventdate is current time, createuser is current login user, createdate is current time, and eventID automatically generates LASTEVENTID as last event ID.

According to embodiments of the present disclosure, recipe information and operational event records for a recipe are all persisted in an Oracle database.

FIG. 12 is a modeling tool architecture diagram for recipe modeling in accordance with an embodiment of the present disclosure.

According to embodiments of the present disclosure, recipe modeling is performed in a modeling tool. As shown in FIG. 12, the modeling tools include recipe modeling, version control, freeze activation, modification rights control, recipe selection rule configuration, and recipe lifecycle management. Wherein the recipe modeling is used for recipe grouping modeling, logical recipe modeling, and recipe modeling. In addition, the recipe-related data is sent to the database for persistence via the TCP/IP protocol after being maintained in the modeling tool. The database may store recipe information, recipe grouping information, recipe operation history information, and the like. Such as, but not limited to, an Oracle database.

Fig. 13 is a block diagram of a user operated platform according to an embodiment of the present disclosure.

As shown in fig. 13, the user operation platform includes a client interface, a server, and a database. The client interface is used for production and manufacturing processes, recipe recommendation and selection control, recipe life cycle management and the like. The client interface was developed based on the WinForm and INFRAGISTICS frameworks. The service end includes unified query service (QRY service), unified scheduling service (CNM service), and OIC (Operator INTERFACE CLIENT) and EAP (Equipment Automation Programming) processing service (CNX service). The system comprises a CNM service, a client and other system interface messages, wherein the unified query service, the client and other system interface messages are firstly distributed through the CNM service, and the client query type messages are uniformly distributed to the QRY service for processing. The unified dispatch service, the client and other system interface messages, firstly, the message is distributed to the corresponding service processing through the CNM service, besides the message distribution load balancing, the abnormal message processing interception can be carried out, and the message data statistics and the like are similar to the gateway function. OIC and EAP process service, mainly deal with the relevant operation of Lot of customer end message and EAP message. The system also has more services such as TIMESrv to handle timing tasks, ERPSrv to handle ERP (Enterprise Resource Planning) system messages, etc., all distributed uniformly by CNMs.

Service end was developed based on sping boot and sping MVC frameworks and the business execution process employed Bpel. Bpel is an XML-based programming language used to describe business processes. The method comprises the steps that a user inputs production information and inquires on a client, and a result of the production information can be sent to a background server through a middleware TIBCO render.

The configuration method can be applied to a production system, and the production system can be Manufacturing Execution System manufacturing execution system, namely ziSEMI MES system. The MES system is a system for whole-flow manufacturing management of a semiconductor sealing and testing factory, and realizes the optimized management of the whole production process by carrying out real-time state tracking from production order execution to product completion and equipment resource. When a real-time event occurs at the factory, the MES can respond to this in time, report it, and instruct and process it with current accurate data. Through implementing information sharing and flow automation of factories, the production efficiency and yield are improved to the maximum extent, thereby achieving the purposes of reducing production cost and improving production management. The MES system adopts a modularized design, and can meet the production requirements of different sealing and measuring process technologies, so that the maximum input-output ratio is realized, and the high flexibility and the personalized production mode required by industry 4.0 are achieved.

Fig. 14 is a business function architecture diagram of a production system according to an embodiment of the present disclosure.

As shown in fig. 14, a production system 1400 according to an embodiment of the present disclosure includes a base data module 1401, a process flow management module 1402, a production planning module 1403, an in-process management module 1404, a lot management module 1405, an engineering management module 1406, a process recipe management module 1407, a device management module 1408, an limits management module 1409, a carrier management module 1410, a materials management module 1411, a jig management module 1412, and a packaging management module 1413.

The base data module 1401 provides system base data modeling functions for the MES system, including factory modeling, equipment modeling, system state modeling, package form modeling, user authority modeling, recipe base data modeling, material base data modeling, process flow modeling, strategy modeling, data collection base data modeling, and alarm base data modeling. The base data module 1401 is a unified base data model platform. The basic data module 1401 provides basic general functions required by a client as a standard framework, and provides a series of custom extension settings such as unified naming standards, unified data enumeration types and unified service management, which is beneficial to rapid construction of an application program. In addition, the base data module 1401 is capable of normalizing the definition of objects in a cross-multi-application, supporting multilingual and multi-unit. Because many elements are defined by the clients, the system becomes more flexible and scalable. The factory modeling supports maintenance of factory basic data, supports multi-factory mode and supports creation of areas under factories. Device modeling supports creation of device master data and device port data maintenance. The system state modeling supports batch state maintenance, equipment state maintenance, material state maintenance, carrier state maintenance, fixture state maintenance, and the like. The package form modeling is used for maintaining the related attribute data of the package, and uniformly maintaining and managing the package modes with different specifications. The user authority modeling supports the creation and maintenance of users, user groups and user roles, and supports the maintenance of user menus and user operation interface password verification. The protocol basic data modeling supports the creation and maintenance of process recipe data and the maintenance of the protocol equipment data relationship. The modeling of the material basis data supports the creation and maintenance of the material basis data. The process step flow modeling supports the creation and maintenance of basic data of process steps, working procedures, working sections and flows, the visual interface editing of the flows, the creation and maintenance of branch flows and the creation and maintenance of reworking flows. Policy modeling supports product level, process level, and process level flow modeling. The system selects different devices and the recops to perform business operation in the actual production process according to different strategy configurations. The data acquisition basic data modeling supports the creation and maintenance of data acquisition detail items and the maintenance of data acquisition rules. The alarm basic data modeling supports alarm system information maintenance, supports maintenance management of alarm triggering conditions, and supports maintenance management of alarm triggering follow-up actions.

The process flow management module 1402 is a completely new set of flow management specifications provided by the MES system. The process flow management module 1402 allows a user to define a product and its corresponding process flow, including each process step type and associated flow control policies.

In terms of version control, the MES system provides a complete version control mechanism, and all processes for activating the production in the MES system must strictly adhere to the version control system, so that production accidents caused by production process data errors are prevented. In terms of flow definition, the process flow management module 1402 supports multi-path selection and may automatically perform path selection based on preset conditions during field operations. The process flow management module 1402 also supports control of various product flow rules, which can be controlled differently according to different conditions of the product and the flow. The conditions can be subdivided into, for example, process steps, product steps, batch steps, etc.

The process step flow modeling supports the creation and maintenance of basic data of the process steps, working procedures, working sections and flows, the visual interface editing of the flows, the creation and maintenance of branch flows and the creation and maintenance of reworking flows.

The product flow configuration can be realized according to different technological flows of different products, and different recops and devices can be selected according to different strategies under the same product flow.

The production plan management module 1403 manages production plan orders and production work orders for the MES system. The user can create a production planning order in the MES system and then re-create a work order according to the planning order. The user can set the priority of the corresponding planning order and the work order in the MES system, set the related information such as the planning order and the work order planning time, and the like, and is convenient for tracking the completion condition of the order in the production and manufacturing process. Wherein the planned order may create and maintain the planned orders for different factories and may control priority and last delivery time. The worksheet creates different worksheets according to different planning orders and may specify particular attributes on the worksheet such as priority, owner, process notes, etc.

The product management module 1404 is used for product processing management, and guides an operator to process products according to preset process requirements, and detailed tracking and recording of processing information are performed. The most important job management function of the product management module 1404 is to allow multiple batches to be processed simultaneously and provide historical traceability of the batches. In addition to the usual creation of lots, inbound, outbound, other functions of the product management module 1404 include batch, batch-in, pause, release, skip, future actions, in-station rework, out-of-station rework, batch rejection, batch cancellation rejection, batch designation of carriers, special business batch outbound, batch-in outbound, multi-core bonding inbound, build-in-out, etc.

The major functions of the batch management module 1405 include batch-to-batch, batch-to-cancel, specified carrier, batch-to-pause, batch-to-cancel, etc.

The project management module 1406 manages project related services in the MES system, and the module functions comprise on-duty license management, QTime management, BOM management, flow card management and batch reservation. The on-duty certificate management provides the user with information related to the on-duty certificate, and sets the expiration time. For whether a user of the card control system has corresponding authority when operating an OIC (Operator INTERFACE CLIENT) system. QTime is used for setting QTime rules and performing rule clamping control when a batch passes through a station. BOM management supports maintenance of BOM and is used for controlling material verification of equipment material loading. The flow card management supports creation and maintenance of flow cards within the system. The production can generate corresponding flow card information according to different flow cards for producing the circulation paper certificates. The batch reservation supports a batch reservation production function.

The process recipe management module 1407 contains process recipe information for all process flows and can create and update process recipes. The set-up usage of the process recipe is version controlled including create, activate, freeze, cancel functions, etc. The process recipe management module 1407 supports the setting of logical process recipes and actual process recipes, such as process parameters, and may automatically select a process recipe based on previous layer measurements based on process condition settings. The process recipe management module 1407 also supports maintenance of equipment and process recipe relationships.

The device management module 1408 provides device basic information definition, provides device state model establishment and tracking management, and supports device authority management, device point inspection, maintenance, repair, and maintenance process management. Wherein, the equipment basic data maintenance is used for maintaining the equipment basic data. The equipment spot inspection supports maintenance of equipment spot inspection items and periodic spot inspection control of equipment. The equipment maintenance supports equipment maintenance and maintenance period setting, and performs maintenance control on the equipment. The equipment report support equipment report function. Equipment maintenance supports equipment maintenance flow tracking. The device ledger supports querying of device-related profile data.

The limit management module 1409 provides control functions for the MES limits. The limit management module 1409 supports setting of limit conditions in different scenarios for controlling whether the batch can support production.

According to the equipment setting, a rule in a certain scene can be set according to the specific condition of the equipment, and when the batch encounters the rule in production and manufacture, the batch cannot be produced through the limit.

According to the product setting, a rule in a certain scene can be set according to the specific condition of the product, and when the batch encounters the rule in the production and manufacture, the batch cannot be produced through the limit.

According to the process flow setting, a rule in a certain scene can be set according to the specific condition of the process flow, and when the batch encounters the rule in production and manufacture, the batch cannot pass the limit production.

The positive and negative item sets that a positive rule can be set, for example, the production is allowed under the rule, and the negative item is not allowed under the condition.

The carrier management module 1410 supports management of carrier related services including creating carriers, cleaning carriers, binding carriers, unbinding carriers, suspending carriers, releasing carriers, and the like. The carrier management module 1410 also supports carrier life management, support usage number management, and support carrier type management. Wherein the vehicle creation is used for creation of vehicle data. The cleaning vehicle is used for new vehicles and for re-cleaning of the vehicle after use. The binding vehicle supports binding of vehicle data and batches. The unbinding carrier supports unbinding operations of the carrier and batch data. The pause carrier performs pause control on the carrier. And releasing the carrier to resume the suspended carrier.

The material management module 1411 includes management of raw materials, semi-finished products, product data, warehouse, goods space, and shelves. The module can be used alone or used as an extension of a storehouse management module in ERP to realize interface functions, and can also be managed and controlled alone. The material management module 1411 supports common warehouse management functions such as material maintenance, material acceptance, material loading, material unloading, finished product warehouse entry, finished product warehouse exit, warehouse transfer and the like.

The jig management module 1412 supports management of jig related services, including creating a jig, cleaning the jig, loading the jig, unloading the jig, suspending the jig, releasing the jig, warehousing the jig, ex-warehouse the jig, moving the jig, scrapping the jig, removing the jig from the line side warehouse, and the like. The jig management module 1412 also supports lifetime management and usage number management of the jig, and management of jig types. Wherein, the jig creation is used for the creation of jig data. The jig cleaning supports the cleaning operation of the jig. The fixture is on-machine to support fixture and equipment binding. The fixture is taken off the machine to support the fixture and the equipment to be unbound. The pause jig supports the pause operation of the jig. The release jig supports the release operation of the jig. The jig warehouse-in supports the warehouse-in operation of the jig. The jig ex-warehouse supports the ex-warehouse operation of the jig. The jig moving warehouse supports the replacement warehouse operation of the jig. The scrapping of the jig supports the scrapping treatment of the jig. The fixture is canceled from being scrapped to support the operation of recovering the scrapped fixture. The fixture wire-withdrawing side bin supports fixture wire-withdrawing side bin operation.

The package management module 1413 supports management of package related services including package in-store, package out-of-store, package code production and printing, package unpacking, package scrapping, package cancellation scrapping. Wherein, the package warehouse-in is used for warehouse-in business after batch package. And the package ex-warehouse is used for the ex-warehouse business after the batch package. The package code production and printing support package generation package code and support printing service. Packaging and unpacking, namely carrying out unpacking operation on the packaged batch. The package discard is performed on the already packaged batch. The package cancellation discard supports a return to use operation on a batch of packages that have been discarded.

Fig. 15 is a system technical architecture diagram of a production system according to an embodiment of the present disclosure.

The technical architecture of the production system according to the embodiments of the present disclosure is developed based on a Client-Server (C/S) architecture model, the Server is responsible for data management, and the Client is responsible for completing the task of interaction with the user. The client module is divided into two parts, one part is used for basic data modeling and is named FactoryModeler (Modeler), and the other part is used for an operation interaction interface of a user and is named Operator INTERFACE CLIENT (OIC).

As shown in fig. 15, the technical architecture of the production system according to an embodiment of the present disclosure includes a presentation layer, an access layer, an application layer, CICD (continuous integration/continuous deployment) layer, and a resource layer. The presentation layer develops a framework based on WinForms and ziOIC of INFRAGISTICS and selects C# language for development. The message middleware of the access layer selects Tibco Rendezvous/RabbitMQ. The application layer includes communications, data, technical components, and languages/frameworks. The communication serialization selects XML/JSON, the protocol selects Rest API, TRDP/RVCM (Tibrv), AMQP (RabbitMQ), the data connection selects HikariCP/DBCP2, the mapping selects Mybatis/ziORM, the Log selects Log4j2, the relation selects Oradle/Gauss, the message queue of the technical component selects Tibrv/RabbitMQ, the business process selects ziFlow Designer & Engine, the development framework of language/framework adopts Spring Boot 2, the development language adopts Java 8, and the timer adopts Spring schedule/Quartz. The CICD layer comprises compiling, packaging, publishing, monitoring and application containers. The compiling, packaging and publishing method selects Maven/Jenkins, selects Zabbix for monitoring and selects built-in Tomcat for an application container. The resource layer includes computing, storage, and operating systems. The computing adopts a physical machine or a cloud virtual machine, RDS, the storage adopts a physical disk or a cloud virtual machine, and the operating system adopts HPUX/Linux/Windows.

Fig. 16A and 16B are application architecture diagrams of a production system according to an embodiment of the present disclosure.

As shown in fig. 16A and 16B, according to the CS architecture selected by the application architecture of the production system according to the embodiment of the present disclosure, the c# language development used by the OIC client engineering page mainly implements the operation of user interaction page data, the display of query page data, the main service interface code is under mes-be-oic\mes. Module\views, the Common components are under mes-be-oic\mes. Command files, the Server end engineering encapsulates a unified development framework ziFrame, including ORM, ESB (TibcoRV), BPEL Engine, exception mechanism, log, internationalization, command-jdtis, transaction, bc pool, message (xml parsing), and the like, and supports xml Message formats with front-end Message communication. The Server end mes-core layer realizes the core service logic processing, and the mes-solution layer provides a service entrance and a custom function realization. The core layer function code module at the server end is as follows: zisemi-mes-be-boot (main system framework, springBoot), zisemi-mes-be-query (query module of all direct acquired data in OIC system, front end unified request XML format, back end unified data response XML format, unique difference: different services, request data is different), zisemi-mes-be-policy (module code of system about production policy in basic data configuration module), zisemi-mes-be-schedule (timer function in system), server side solution code module is zisemi-mes-code (OIC service core code area, so service needs to enter the module for service processing), zisemi-mes-data (all data model in OIC system, javabean object), zisemi-mes-be-solution (entrance of OIC service code, so front end requested XML is processed according to TibcoRV message middleware mechanism, then corresponding to different sub-files under the module, entering corresponding to the entrance of the module code, and corresponding to the step code of flow code of the module is 3998-flow code, corresponding to the step code of the corresponding to the step of flow module is 3998-flow (flow code of the corresponding to the corresponding module of flow-flow code of the system).

As shown in fig. 17, the electronic device 1700 according to the embodiment of the present disclosure includes a processor 1701 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 1702 or a program loaded from a storage portion 1708 into a Random Access Memory (RAM) 1703. The processor 1701 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special-purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. The processor 1701 may also include on-board memory for caching purposes. The processor 1701 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the disclosure.

In the RAM 1703, various programs and data necessary for the operation of the electronic device 1700 are stored. The processor 1701, the ROM 1702, and the RAM 1703 are connected to each other through a bus 1704. The processor 1701 performs various operations of the method flow according to an embodiment of the present disclosure by executing programs in the ROM 1702 and/or the RAM 1703. Note that the program may be stored in one or more memories other than the ROM 1702 and the RAM 1703. The processor 1701 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in one or more memories.

According to an embodiment of the disclosure, the electronic device 1700 may also include an input/output (I/O) interface 1705, the input/output (I/O) interface 1705 also being connected to the bus 1704. The electronic device 1700 may also include one or more of an input portion 1706 including a keyboard, mouse, etc., an output portion 1707 including a display such as a Cathode Ray Tube (CRT), liquid Crystal Display (LCD), etc., and speaker, etc., a storage portion 1708 including a hard disk, etc., and a communication portion 1709 including a network interface card such as a LAN card, modem, etc., connected to the I/O interface 1705. The communication section 1709 performs communication processing via a network such as the internet. The driver 1710 is also connected to the I/O interface 1705 as needed. A removable medium 1711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on the drive 1710, so that a computer program read therefrom is installed into the storage portion 1708 as needed.

The present disclosure also provides a non-transitory computer readable storage medium that may be included in the apparatus/device/system described in the above embodiments, or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but is not limited to, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, the computer-readable storage medium may include ROM 1702 and/or RAM 1703 described above and/or one or more memories other than ROM 1702 and RAM 1703.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowcharts. The program code, when executed in a computer system, causes the computer system to implement a method of verifying process data for a product provided by embodiments of the present disclosure.

The above-described functions defined in the system/apparatus of the embodiments of the present disclosure are performed when the computer program is executed by the processor 1701. The systems, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program can also be transmitted in the form of signals over a network medium, distributed, and downloaded and installed via the communication portion 1709, and/or from the removable medium 1711. The computer program may comprise program code that is transmitted using any appropriate network medium, including but not limited to wireless, wireline, etc., or any suitable combination of the preceding.

In such an embodiment, the computer program can be downloaded and installed from a network via the communication portion 1709, and/or installed from the removable media 1711. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 1701. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

According to embodiments of the present disclosure, program code for performing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, such computer programs may be implemented in high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. Programming languages include, but are not limited to, such as Java, c++, python, "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be provided in a variety of combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.

The embodiments of the present disclosure are described above. These examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.

Claims

A method of configuring a production system, the production system including a plurality of production devices, the method comprising:

creating a recipe for the plurality of production devices based on the user input data, wherein each production device is associated with one or more recipes;

In response to a configuration request for at least one production device of the plurality of production devices, determining a recipe selection rule applicable to the configuration request from a preset plurality of recipe selection rules;

Selecting a recipe matching the configuration request from the created plurality of recipes according to the determined recipe selection rule;

the production equipment associated with each recipe is configured with the selected recipe.
The method of claim 1, wherein each recipe selection rule has a priority, and wherein determining a recipe selection rule applicable to the configuration request from among a preset plurality of recipe selection rules comprises:

Extracting recipe query information for the at least one production device from the configuration request;

Among the plurality of recipe selection rules, a recipe selection rule having a highest priority that matches the recipe query information is determined as a recipe selection rule applicable to the recipe matching request.
The method of claim 2, wherein each recipe selection rule specifies at least one data item to be compared, the priority of each recipe selection rule being determined based on the number of data items specified by the recipe selection rule, the greater the number of data items, the higher the priority.
The method of claim 3, wherein the determining, among the plurality of recipe selection rules, a recipe selection rule having a highest priority that matches the recipe query information as a recipe selection rule applicable to the recipe matching request comprises:

sequentially determining whether the data items designated by each formula selection rule are a subset or a whole set of the data items related to the formula query information according to the order of the priority from high to low;

If the data items specified by the current recipe selection rule are a subset or a complete set of the data items related to the recipe query information, determining that the current recipe selection rule matches the recipe query information, otherwise determining that the current recipe selection rule does not match the recipe query information.
The method of claim 3 or 4, wherein the plurality of recipe selection rules includes a product level selection rule, a process level selection rule, and a process level selection rule, a priority of the product level selection rule being higher than a priority of the process level selection rule, the priority of the process level selection rule being higher than a priority of the process level selection rule.
The method of claim 5, wherein,

The data items specified by the product level selection rules include data items related to products, data items related to main processes and sub-processes of the process, data items related to process steps and data items related to recipes,

The data items specified by the process level selection rules comprise data items related to a main process flow and a sub process flow of the process, data items related to a process step and data items related to a recipe;

the data items specified by the process step selection rules include data items relating to process sub-flows, data items relating to process steps, and data items relating to recipes.
The method of any of claims 1 to 6, wherein each recipe selection rule specifies at least one data item to be compared, the selecting a recipe from the created plurality of recipes that matches the configuration request according to the determined recipe selection rule comprising:

For each recipe, it is determined whether the value in the recipe for each recipe data item defined by the determined recipe selection rule matches the value in the configuration request, and if so, the recipe is determined to be one of the recipes that match the configuration request.
The method of any of claims 1-7, wherein the creating a recipe for the plurality of production devices from user input data comprises:

Creating at least one recipe packet based on recipe packet information entered by a user, the recipe packet including packet logic indicating a production device and a recipe path corresponding to each recipe packet, wherein the recipe path is used to find a recipe in the recipe packet;

adding at least one recipe to a recipe group based on recipe information input by a user for the recipe group;

And determining production equipment and a logic recipe corresponding to each recipe in the recipe group according to the grouping logic of the recipe group, and associating the data model of the recipe with the production equipment and the logic recipe corresponding to the recipe.
The method of claim 8, wherein at least one of the recipe group and the recipe has an activation status that indicates whether the corresponding recipe group or recipe is available.
The method of claim 9, further comprising determining whether each recipe to be added is available based on an activation status of a recipe before adding at least one recipe to the recipe group;

Wherein the adding at least one recipe to the recipe group comprises adding a recipe available from the at least one recipe to the recipe group.
The method of any one of claims 8 to 10, further comprising editing at least one of the recipe group and the recipe according to a user operation, the editing including modifying, deleting, and raising.
The method of claim 11, wherein at least one of the recipe group and the recipe has a frozen state indicating whether the corresponding recipe group or recipe is editable.
The method of any one of claims 8 to 12, further comprising modeling data for a plurality of candidate recipes, respectively, wherein the adding at least one recipe to a recipe group based on recipe information entered by a user for the recipe group comprises:

from the plurality of candidate recipes, selecting a data model of a candidate recipe that matches a recipe name in recipe information as a data model of a recipe in the recipe group.
The method of claim 13, wherein separately modeling the plurality of candidate recipes comprises, for each candidate recipe,

Importing or creating a data model of the candidate formula from a database;

And setting the freezing state of the data model of the candidate formula to be non-editable according to the freezing operation of the user.

And setting the activation state of the data model of the candidate formula to be available according to the activation operation of the user.
The method of claim 14, further comprising, after importing or creating a data model of the candidate recipe from a database,

In response to receiving a start editing instruction for a data model of the candidate recipe, starting the editing of the data model of the candidate recipe according to an editing operation by a user;

ending the editing of the data model of the candidate recipe according to the editing operation of the user in response to receiving an ending editing instruction for the data model of the candidate recipe,

Wherein editing of the data model of the candidate recipe by other users than the user is prohibited for a period of time after receiving the instruction to start editing and before receiving the instruction to end editing.
The method of any one of claims 1 to 15, further comprising:

storing the operational event in association with the recipe in response to a user operational event for the recipe, wherein the operational event for the recipe includes at least one of creation, editing, cloning, freezing, unfreezing, activating, deactivating, raising, using of the recipe, and

In response to a query request for a recipe for which a specified operational event occurred, a recipe associated with the specified operational event is determined among a plurality of stored recipes.
An electronic device comprising a memory and a processor, the memory having stored therein instructions executable by the processor, which when executed by the processor, cause the processor to perform the method of any of claims 1 to 16.
A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1 to 16.
A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 16.